Pin fixtures to use postgresql 2.5.0

Unfortunately postgresql master is not compatible with this module yet, so to
avoid errors during testing we are having to pin the revision of postgresql
we pull down.

Unfortunately again, puppetlabs_spec_helper doesn't yet support branches, so
we're pinning on a specific revision for now.

This can be removed once we are modified to be compatible with the newly
released postgresql module.

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #86 from kbarber/maint/master/pin_postgresql_fixtures_to_250

Pin fixtures to use postgresql 2.5.0
Release 2.0.0

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>
FM-103: Add metadata.json to all modules.

I've been asked to add metadata.json to all modules.  I've just
listed the main RedHat/Debian distros as supported for now.
Add soft_write_failure to puppetdb.conf

This supports a recently added feature to PuppetDB.
Merge pull request #85 from kbarber/ticket/master/release-20

Release 2.0.0
This will pin the installation of puppetlabs/postgresql to version 2.5.0

Since version 3.0.0 is now released, we want to pin against the old revision
everywhere. We already pin in the Modulefile and unit tests, we just forgot
to do it for the rspec-system tests.

Signed-off-by: Ken Barber <ken@bob.sh>
Add params to support soft_write_failure option as per Ken Barber

I can rebase these commits once the code is debugged and to your
liking.
Merge pull request #90 from kbarber/maint/master/pin-system-tests-to-old-postgresql-module

This will pin the installation of puppetlabs/postgresql to version 2.5.0
Document puppetdb_soft_write_failure in README
Update metadata.json

Make Puppet versions strings, and update for 2.0.
Merge pull request #89 from ghoneycutt/soft_write_failure

Add soft_write_failure to puppetdb.conf
Merge pull request #87 from apenney/metadata

FM-103: Add metadata.json to all modules.
Add switch to configure database SSL connection

PostgreSQL supports secure connections through SSL. For PuppetDB
to connect with SSL, "?ssl=true" has to be specified on the
connection string.

This patch adds such a switch, by default PuppetDB will not use SSL
to connect to the database.
Disable database validation, if SSL is enabled
Document new database_ssl option in README