|
| 1 | +2013-10-01 - Version 3.0.0 |
| 2 | + |
| 3 | +Summary: |
| 4 | + |
| 5 | +Version 3 was a major rewrite to fix some internal dependency issues, and to |
| 6 | +make the new Public API more clear. As a consequence a lot of things have |
| 7 | +changed for version 3 and older revisions that we will try to outline here. |
| 8 | + |
| 9 | +(NOTE: The format of this CHANGELOG differs to normal in an attempt to |
| 10 | +explain the scope of changes) |
| 11 | + |
| 12 | +* Server specific objects now moved under `postgresql::server::` namespace: |
| 13 | + |
| 14 | +To restructure server specific elements under the `postgresql::server::` |
| 15 | +namespaces the following objects were renamed as such: |
| 16 | + |
| 17 | +`postgresql::database` -> `postgresql::server::database` |
| 18 | +`postgresql::database_grant` -> `postgresql::server::database_grant` |
| 19 | +`postgresql::db` -> `postgresql::server::db` |
| 20 | +`postgresql::grant` -> `postgresql::server::grant` |
| 21 | +`postgresql::pg_hba_rule` -> `postgresql::server::pg_hba_rule` |
| 22 | +`postgresql::plperl` -> `postgresql::server::plperl` |
| 23 | +`postgresql::contrib` -> `postgresql::server::contrib` |
| 24 | +`postgresql::role` -> `postgresql::server::role` |
| 25 | +`postgresql::table_grant` -> `postgresql::server::table_grant` |
| 26 | +`postgresql::tablespace` -> `postgresql::server::tablespace` |
| 27 | + |
| 28 | +* New `postgresql::server::config_entry` resource for managing configuration: |
| 29 | + |
| 30 | +Previously we used the `file_line` resource to modify `postgresql.conf`. This |
| 31 | +new revision now adds a new resource named `postgresql::server::config_entry` |
| 32 | +for managing this file. For example: |
| 33 | + |
| 34 | +```puppet |
| 35 | + postgresql::server::config_entry { 'check_function_bodies': |
| 36 | + value => 'off', |
| 37 | + } |
| 38 | +``` |
| 39 | + |
| 40 | +If you were using `file_line` for this purpose, you should change to this new |
| 41 | +methodology. |
| 42 | + |
| 43 | +* `postgresql_puppet_extras.conf` has been removed: |
| 44 | + |
| 45 | +Now that we have a methodology for managing `postgresql.conf`, and due to |
| 46 | +concerns over the file management methodology using an `exec { 'touch ...': }` |
| 47 | +as a way to create an empty file the existing postgresql\_puppet\_extras.conf |
| 48 | +file is no longer managed by this module. |
| 49 | + |
| 50 | +If you wish to recreate this methodology yourself, use this pattern: |
| 51 | + |
| 52 | +```puppet |
| 53 | + class { 'postgresql::server': } |
| 54 | + |
| 55 | + $extras = "/tmp/include.conf" |
| 56 | + |
| 57 | + file { $extras: |
| 58 | + content => 'max_connections = 123', |
| 59 | + notify => Class['postgresql::server::service'], |
| 60 | + }-> |
| 61 | + postgresql::server::config_entry { 'include': |
| 62 | + value => $extras, |
| 63 | + } |
| 64 | +``` |
| 65 | + |
| 66 | +* All uses of the parameter `charset` changed to `encoding`: |
| 67 | + |
| 68 | +Since PostgreSQL uses the terminology `encoding` not `charset` the parameter |
| 69 | +has been made consisent across all classes and resources. |
| 70 | + |
| 71 | +* The `postgresql` base class is no longer how you set globals: |
| 72 | + |
| 73 | +The old global override pattern was less then optimal so it has been fixed, |
| 74 | +however we decided to demark this properly by specifying these overrides in |
| 75 | +the class `postgresql::global`. Consult the documentation for this class now |
| 76 | +to see what options are available. |
| 77 | + |
| 78 | +Also, some parameter elements have been moved between this and the |
| 79 | +`postgresql::server` class where it made sense. |
| 80 | + |
| 81 | +* `config_hash` parameter collapsed for the `postgresql::server` class: |
| 82 | + |
| 83 | +Because the `config_hash` was really passing data through to what was in |
| 84 | +effect an internal class (`postgresql::config`). And since we don't want this |
| 85 | +kind of internal exposure the parameters were collapsed up into the |
| 86 | +`postgresql::server` class directly. |
| 87 | + |
| 88 | +* Lots of changes to 'private' or 'undocumented' classes: |
| 89 | + |
| 90 | +If you were using these before, these have changed names. You should only use |
| 91 | +what is documented in this README.md, and if you don't have what you need you |
| 92 | +should raise a patch to add that feature to a public API. All internal classes |
| 93 | +now have a comment at the top indicating them as private to make sure the |
| 94 | +message is clear that they are not supported as Public API. |
| 95 | + |
| 96 | +* `pg_hba_conf_defaults` parameter included to turn off default pg\_hba rules: |
| 97 | + |
| 98 | +The defaults should be good enough for most cases (if not raise a bug) but if |
| 99 | +you simply need an escape hatch, this setting will turn off the defaults. If |
| 100 | +you want to do this, it may affect the rest of the module so make sure you |
| 101 | +replace the rules with something that continues operation. |
| 102 | + |
| 103 | +* `postgresql::database_user` has now been removed: |
| 104 | + |
| 105 | +Use `postgresql::server::role` instead. |
| 106 | + |
| 107 | +* `postgresql::psql` resource has now been removed: |
| 108 | + |
| 109 | +Use `postgresql_psql` instead. In the future we may recreate this as a wrapper |
| 110 | +to add extra capability, but it will not match the old behaviour. |
| 111 | + |
| 112 | +* `postgresql_default_version` fact has now been removed: |
| 113 | + |
| 114 | +It didn't make sense to have this logic in a fact any more, the logic has been |
| 115 | +moved into `postgresql::params`. |
| 116 | + |
| 117 | +* `ripienaar/concat` is no longer used, instead we use `puppetlabs/concat`: |
| 118 | + |
| 119 | +The older concat module is now deprecated and moved into the |
| 120 | +`puppetlabs/concat` namespace. Functionality is more or less identical, but |
| 121 | +you may need to intervene during the installing of this package - as both use |
| 122 | +the same `concat` namespace. |
| 123 | + |
1 | 124 | 2013-09-09 Release 2.5.0 |
2 | 125 | ======================= |
3 | 126 |
|
|
0 commit comments