conditionally do not manage the postgres server itself, so users can separately declare postgresql::server and pass whatever options they want.
remove duplicated documentation of puppetdb::database::postgresql manage_firewall parameter
fix module description in NOTICE
Use $is_pe for PE determination

...rather than the custom logic that was used previously. Using a
uniform canon fact across all modules that need to differentiate between
PE and POSS makes unusual situations (such as having a missing
/opt/puppet/pe_version file) more, well, uniform.
Bump version requirement for puppetlabs/stdlib

The is_pe fact was first defined in stdlib in 3.1.0. We want to use that
fact for making the "PE or Not PE" determination in params, so we need
to require a stdlib at least that new. Note that at the time of commit
the current version of stdlib is 4.1.0, so we're not exactly requiring
bleeding edge.
Merge pull request #122 from reidmv/use_is_pe

Use $is_pe for PE determination
Fix is_pe declaration so it works without is_pe

Signed-off-by: Ken Barber <ken@bob.sh>
Test against string 'true' not boolean

Because facter likes to convert booleans to strings

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

Fix is_pe declaration so it works without is_pe
Add strict_variables support when puppetdb is not on puppetmaster
Add unit tests for puppetdb::master::config
Add STRICT_VARIABLES support in travis with puppet > 3.5
Fix strict_variables issue
Merge pull request #126 from mcanevet/fix/strict_variables

Add strict_variables support when puppetdb is not on puppetmaster
Merge pull request #121 from jantman/conditional_db

Parameter to not manage postgresql server
Auto enable strict_variables for unit tests when puppet > 3.5
Merge pull request #129 from mcanevet/feature/enable_strict_variables

Auto enable strict_variables for unit tests when puppet > 3.5