This updates the module to be able to use puppetlabs-postgresql.
Since this change is a major change, it marks this patch as a breaking change.
I have prepared a suitable amount of upgrade notes for upgrading to this later
version of the module plus removed anything marked deprecated.
As cleanup, I've removed the troublesome 'tests' directory in favour of good
README.md documentation. I've also removed any puppet docs from each module
until such times as puppet docs become automated through the forge. This is
just to avoid contributors having to double their efforts - the README.md
is the authority now.
Signed-off-by: Ken Barber <ken@bob.sh>
This modifies the CHANGELOG for the 2.0.0 release, and adds an upgrading
section to warn users about the `inifile` change during the upgrade.
Signed-off-by: Ken Barber <ken@bob.sh>
Downcase has been added to puppetlabs/puppetdb, this patch changes the
dependency for stdlib to >= 2.2.0 as that was when downcase was first
included.
Signed-off-by: Ken Barber <ken@bob.sh>
Previously this was >= 3.2.0, which probably isn't necessary just for
validate_re, plus at the time of writing this it was causing a problem
with the forge.
Signed-off-by: Ken Barber <ken@bob.sh>
Updated CHANGELOG and Modulefile. Added proper ignores for packaging and
removed duplicate release notes from README.md.
Signed-off-by: Ken Barber <ken@bob.sh>
Prior to this commit, the module always attempted
to restart the puppet master service whenever it
managed the master config files. This commit
disables that behavior since our acceptance nodes
don't have the service installed.
Prior to this commit, if you allowed the puppetdb module
to manage postgres for you, it would always try to manage
the firewall for the postgres port on redhat systems.
This commit exposes that as a parameter in a few more
spots, and passes it through to the postgres module.
