postgres-formula/pillar.example

postgres:
  pg_hba.conf: salt://postgres/pg_hba.conf
  use_upstream_repo: False

  pkg: 'postgresql-9.3'
  pkg_client: 'postgresql-client-9.3'
  pkgs_extra:
    - postgresql-contrib
    - postgresql-plpython

  users:
    localUser:
      ensure: present
      password: '98ruj923h4rf'
      createdb: False
      createroles: False
      createuser: False
      inherit: True
      replication: False

    remoteUser:
      ensure: present
      password: '98ruj923h4rf'
      createdb: False
      createroles: False
      createuser: False
      inherit: True
      replication: False

    absentUser:
      ensure: absent
      password: '98ruj923h4rf'
      createdb: False
      createroles: False
      createuser: False
      inherit: True
      replication: False

  # This section cover this ACL management of the pg_hba.conf file.
  # <type>, <database>, <user>, [host], <method>
  acls:
    - ['local', 'db1', 'localUser']
    - ['host', 'db2', 'remoteUser', '123.123.0.0/24']

  tablespaces:
    my_space:
      directory: /srv/my_tablespace
      owner: localUser

  databases:
    db1:
      owner: 'localUser'
      template: 'template0'
      lc_ctype: 'en_US.UTF-8'
      lc_collate: 'en_US.UTF-8'
      # optional schemas to enable on database
      schemas:
        uuid_ossp:
          owner: localUser
      # optional extensions to enable on database
      extensions:
        uuid-ossp:
          schema: uuid_ossp
    db2:
      owner: 'localUser'
      user: 'remoteUser'
      template: 'template0'
      lc_ctype: 'en_US.UTF-8'
      lc_collate: 'en_US.UTF-8'
      tablespace: 'my_space'
      # optional extensions to enable on database
      # extensions:
      #   postgis:
  # backup extension defaults to .bak if postgresconf_backup is True.
  # Set to False to stop creation of backup on postgresql.conf changes.
  postgresconf_backup: True
  # This section will append your configuration to postgresql.conf.
  postgresconf: |
    listen_addresses = 'localhost,*'
Add pillar example 2014-05-06 11:48:21 -06:00			`postgres:`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00			`pg_hba.conf: salt://postgres/pg_hba.conf`
Switch to new style map.jinja Move this formula to the new style map.jinja. Still need to sort out RedHat handling, but it's not any worse than it was before (i.e. horribly broken) 2015-04-22 17:47:02 -05:00			`use_upstream_repo: False`
Add option to use upstream repo on Debian 2015-02-01 14:40:45 +00:00
- re-arrange cluster initialization to a set of variables in a dictionary which control three things: 1. should we initialize? 2. if so, how? 3. what environment variables and user to use The approach taken is very similar to what the Apache formula uses, namely: a default dictionary which is over-ridden by: os-specific defaults, then os codename defaults, then os finger defaults, and finally user-specified pillar values - this also adds support for grains['osfinger'] 2016-07-08 15:34:45 -05:00			`pkg: 'postgresql-9.3'`
			`pkg_client: 'postgresql-client-9.3'`
			`pkgs_extra:`
			`- postgresql-contrib`
			`- postgresql-plpython`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00
			`users:`
			`localUser:`
added option to remove users 2015-10-06 13:24:53 +02:00			`ensure: present`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00			`password: '98ruj923h4rf'`
			`createdb: False`
added examples of new user options to pillar.example 2015-05-05 15:10:34 -07:00			`createroles: False`
			`createuser: False`
			`inherit: True`
			`replication: False`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00
			`remoteUser:`
added option to remove users 2015-10-06 13:24:53 +02:00			`ensure: present`
			`password: '98ruj923h4rf'`
			`createdb: False`
			`createroles: False`
			`createuser: False`
			`inherit: True`
			`replication: False`

			`absentUser:`
			`ensure: absent`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00			`password: '98ruj923h4rf'`
			`createdb: False`
added examples of new user options to pillar.example 2015-05-05 15:10:34 -07:00			`createroles: False`
			`createuser: False`
			`inherit: True`
			`replication: False`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00
			`# This section cover this ACL management of the pg_hba.conf file.`
			`# <type>, <database>, <user>, [host], <method>`
			`acls:`
			`- ['local', 'db1', 'localUser']`
fix host ACL in pillar.example 2014-10-10 22:35:47 -05:00			`- ['host', 'db2', 'remoteUser', '123.123.0.0/24']`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00
Allow to specify a tablespace for a database * Tablespaces have to be created before the databases * Add pillar examples * Add tests 2016-06-08 07:36:28 -03:00			`tablespaces:`
fixes formula to comply to its spec The reworks in merge #110 broke this formulas kitchen based specs. This MR changes a few minor things, mostly pillar.example and other inconsistent documentations. Also, the use of db_user for `postgres_tablespace.present` and `postgres_database.present` now fits the states options, as db_password etc can be specified as well. 2016-08-05 20:22:51 +02:00			`my_space:`
			`directory: /srv/my_tablespace`
			`owner: localUser`
Allow to specify a tablespace for a database * Tablespaces have to be created before the databases * Add pillar examples * Add tests 2016-06-08 07:36:28 -03:00
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00			`databases:`
			`db1:`
			`owner: 'localUser'`
			`template: 'template0'`
- change C.UTF-8 to en_us.UTF-8 in example pillar, as the former does not work on all distributions 2016-07-19 10:10:56 -05:00			`lc_ctype: 'en_US.UTF-8'`
			`lc_collate: 'en_US.UTF-8'`
support options in extensions 2015-11-02 09:41:41 +03:00			`# optional schemas to enable on database`
support schemas 2015-11-02 09:41:41 +03:00			`schemas:`
			`uuid_ossp:`
			`owner: localUser`
support options in extensions 2015-11-02 09:41:41 +03:00			`# optional extensions to enable on database`
Add support for database extensions. This commit adds support for database extensions via salt.states.postgres_extension When configuring database pillar data all you need to do is add (optional) extension list with the extensions that you want the state to apply to specific database. Example: db1: owner: 'localUser' user: 'localUser' template: 'template0' lc_ctype: 'C.UTF-8' lc_collate: 'C.UTF-8' extensions: - uuid-ossp This will make sure `uuid-ossp` extension is enabled on `db1` database. Updated pillar.example to include (optional) extensions 2015-07-23 17:51:24 +03:00			`extensions:`
support options in extensions 2015-11-02 09:41:41 +03:00			`uuid-ossp:`
			`schema: uuid_ossp`
Added support for multiple databases/users 2014-07-27 22:04:57 -04:00			`db2:`
			`owner: 'localUser'`
			`user: 'remoteUser'`
			`template: 'template0'`
- change C.UTF-8 to en_us.UTF-8 in example pillar, as the former does not work on all distributions 2016-07-19 10:10:56 -05:00			`lc_ctype: 'en_US.UTF-8'`
			`lc_collate: 'en_US.UTF-8'`
Allow to specify a tablespace for a database * Tablespaces have to be created before the databases * Add pillar examples * Add tests 2016-06-08 07:36:28 -03:00			`tablespace: 'my_space'`
Add support for database extensions. This commit adds support for database extensions via salt.states.postgres_extension When configuring database pillar data all you need to do is add (optional) extension list with the extensions that you want the state to apply to specific database. Example: db1: owner: 'localUser' user: 'localUser' template: 'template0' lc_ctype: 'C.UTF-8' lc_collate: 'C.UTF-8' extensions: - uuid-ossp This will make sure `uuid-ossp` extension is enabled on `db1` database. Updated pillar.example to include (optional) extensions 2015-07-23 17:51:24 +03:00			`# optional extensions to enable on database`
Allow to specify a tablespace for a database * Tablespaces have to be created before the databases * Add pillar examples * Add tests 2016-06-08 07:36:28 -03:00			`# extensions:`
			`# postgis:`
Added option to disable creation of backup file when postgresql.conf changes 2016-03-14 19:19:32 +00:00			`# backup extension defaults to .bak if postgresconf_backup is True.`
			`# Set to False to stop creation of backup on postgresql.conf changes.`
			`postgresconf_backup: True`
Added the ability to add custom configuration to the postgresql.conf configuration file. 2014-10-06 11:34:43 +02:00			`# This section will append your configuration to postgresql.conf.`
			`postgresconf: \|`
			`listen_addresses = 'localhost,*'`