Commit graph

12 commits

Author SHA1 Message Date
Tim Meusel
1fe0a76032 add ability to manage postgres repo
the module triggers puppetlabs-postgresql which is able to handle yum/apt repos from the postgres devs. Usefull in cases that your operating system doesn't provide the newest release. this feature is disabled by default

fix typo
2015-01-14 14:02:49 +01:00
Ken Barber
f6f6e55b33 Cleanups, missing doc items and new test_url capability
This provides a number of cleanups as the code has been unloved for a while.

I've added the ssl-* parameters the robinbowes added in his last patch to the
docs, and found some other cleanups as well where applicable.

I've added the ability to override the test_url also, so that in the future
if a user wishes to they can customize this.

Signed-off-by: Ken Barber <ken@bob.sh>
2014-10-07 15:06:54 +01:00
Sebastian Reitenbach
5ed5839d48 do not manage firewall for postgres, puppetlabs/postgres module from
git has dropped that silly firewall management support.

do not document removed manage_firewall parameter anymore
2014-08-31 22:36:11 +02:00
Matthias Baur
eac026c658 Allow to set the manage_server parameter in the init class 2014-07-11 11:14:40 +02:00
Jason Antman
2ae8754efe conditionally do not manage the postgres server itself, so users can separately declare postgresql::server and pass whatever options they want. 2014-02-20 15:35:16 -05:00
Ken Barber
603df7381d (GH-93) Switch to using puppetlabs-postgresql 3.x
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>
2013-10-21 18:43:41 +01:00
Erik Dalén
8a30c5a11d Separate DB instance and DB user creation 2013-05-07 18:28:23 +02:00
Karel Brezina
1d83efbcec Database name, user name and password can be set to arbitrary values. 2013-02-13 12:14:53 +01:00
Chris Price
de20b44101 Fix backward compatibility of manage_redhat_firewall parameter
Prior to this commit, the deprecated `manage_redhat_firewall` param
was not actually backward compatible because there were several
cases where we couldn't tell the difference between the user
explicitly specifying `false` for that parameter as opposed to
not specifying it at all.  This commit is a bit ugly because it
sets some defaults to `undef` in order to allow us to tell the
difference between the two cases, but it should resolve backwards
compatibility issues.
2013-01-17 09:59:08 -08:00
Chris Price
f21740b699 Pass 'manage_redhat_firewall' param through to postgres
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.
2012-09-21 10:47:19 -07:00
Garrett Honeycutt
1aab5d98b0 complies with style guide 2012-09-20 14:46:26 -07:00
Chris Price
8fbda3c4d6 Use ini_file to manage settings, and add validation
This commit does the following:

* Use the new inifile module to manage puppet.conf
* More comprehensive management of config files
* Validate database connectivity before applying puppetdb
  config changes
* Validate puppetdb connectivity before applying puppet
  master config changes
* Documentation
2012-09-17 15:26:32 -07:00