This adds a basic test to run the standard 1 node setup until it succeeds.
This also fixes a bug with the connection validation facilities. Before this
patch we would keep retrying the connection to PuppetDB until the timeout
expired, this patch fixes that bug making provisioning faster and well, more
reliable. I've also increased the timeout as some systems take longer than
15 seconds for PuppetDB to start.
Signed-off-by: Ken Barber <ken@bob.sh>
This patch introduces the optional parameter $disable_ssl, which
defaults to false. If set to true, the settings ssl-host and ssl-port
are completely removed from the Jetty section of the PuppetDB config
files.
This disables serving of HTTPS requests by PuppetDB, which can be useful
when SSL handling is offloaded to a reverse proxy server like Apache or
Nginx, as suggested in the PuppetDB documentation (see
http://docs.puppetlabs.com/puppetdb/1.2/connect_puppet_apply.html#option-a-set-up-an-ssl-proxy-for-puppetdb).
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, 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.
