Enable service control for puppetdb #81
Merged
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.
Hello,
I added some bits to the module to allow disabling the puppetdb service, but still have puppetdb deployed and configured . Our use case would be something like this: we have a backup puppetdb machine with postgres in recovery and a puppetdb pointed to that database. We wanted to disable the service so it doesn't try to actually use the database. When we want to switch to the backup machine we just take the database out of recovery mode and enable the puppetdb service.