This repository was archived by the owner on Mar 28, 2019. It is now read-only.
Add basic puppetlabs-puppetdb module integration, deprecate storeconfigs option #128
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use puppetlabs/puppetdb to set up a basic all-in-one puppetmaster
Also alphabetizes prameters in server.pp for convenience
The puppetlabs/puppetdb module is significantly more polished than our existing puppet-puppet capabilities for setting up puppetdb, so I think it makes sense to use it for this functionality. As-is this has it configure the master for puppetdb as well.
Based on my limited testing, this stands up a working all-in-one puppet master / puppetdb / ca using the new test, on Debian Wheezy. Once the pull request for refactoring beaker tests is accepted I'll add a test case that mirrors the use case in
tests/unicorn_with_puppetdb.pp, then add it to documentation once the new setup is actually under test coverage.If others prefer to manage puppetdb from fully within puppet-puppet I'm open to that option.
Further out, I'd like to use this functionality to set up a simple "master-of-masters" option to facilitate bootstrapping a puppet infrastructure, where the initial node would use a setup like this one to bootstrap an all-in-one, then use exported resources to set up additional compile nodes and perhaps a different puppetdb node for nodes connecting to the second-tier nodes.