This documents each of the newer parameters: gc_interval, log_slow_statements,
conn_max_age, conn_keep_alive, conn_lifetime with the version of PuppetDB that
are supported on.
Signed-off-by: Ken Barber <ken@bob.sh>
This patch adds all the missing parameters now defined in the 1.4.0 release.
This includes some new database parameters mainly, but also adds gc_interval
to the `puppetdb` and `puppetdb::server` classes, as previously this wasn't
configurable using this method.
To avoid documentation duplication the Puppet headers have been removed in
favour of documenting classes from the README.md. Until such times as the
forge can turn Puppet docs into HTML automatically, this is just duplicate
noise and prone to update slippage. The README.md is more authoritative in
this area and is pubicly displayed on the forge project page so it should be
used for now.
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>
* Remove .DS_Store from commit as we don't want mac directory metadata files
committed to the repository.
* Removed now irrelevant README_GETTING_STARTED.md as that content is now
merged and thus duplicated in README.md.
* Whitespace cleanups in README.md: trailing spaces, made soft wraps the
standard.
* Replaced instances of 'include' with the 'class' format.
* Fixed Release Notes to reflect the notes from the Forge
Signed-off-by: Ken Barber <ken@bob.sh>
* updates README's formatting to confirm to new PL module standard
* Created TOC linking to major headings in README to enhance readability,
enable a user to find what they need quickly, and to act as a document
guide.
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.
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
The test manifests for single-node (everything installed on
the master machine) now work properly. You have to
edit your puppet.conf by hand to turn on storeconfigs and
point it at puppetdb, but other than that, this successfully
handles everything that you need for either an hsql or
postgres setup.
