Stop managing etc/auth dir contents #71
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The current release installs a directory full of expired certificates into etc/auth. This breaks the kvstore on the search/indexer machines, because mongodb won't start with an expired cert. Additionally, splunk seems to regenerate at least some of these certificates when strting up, leading puppet to fight splunk over the contents and frequent service restarts. I can't see a good reason for this module to be managing the contents of the certificate files; a job best left to the profile or glue module that uses this splunk module, therefore I've removed it entirely.
|
I'm adding my vote for this. |
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Stop managing etc/auth dir contents
The current release installs a directory full of expired certificates into
etc/auth. This breaks the kvstore on the search/indexer machines, because
mongodb won't start with an expired cert.
Additionally, splunk seems to regenerate at least some of these certificates
when starting up, leading puppet to fight splunk over the contents and
frequent service restarts.
I can't see a good reason for this module to be managing the contents of the
certificate files; a job best left to the profile or glue module that uses
this splunk module, therefore I've removed it entirely.