This repository was archived by the owner on Jun 11, 2019. It is now read-only.
Unmanage puppet_manage_package user & group #19
Merged
Conversation
This file contains hidden or 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 splunk package install chowns everything under /opt/splunkforwarder to the splunk user. We can't have this file be owned by the splunk user when we create it, since the package hasn't been installed and the user doens't exist yet. We'll let Puppet create it with the default (probably root) and then let the Splunk package handle it from there. This way Puppet and Splunk don't bicker over who should manage the ownership.
alvagante
added a commit
that referenced
this pull request
May 7, 2014
Unmanage puppet_manage_package user & group
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The splunk package install chowns everything under /opt/splunkforwarder
to the splunk user. We can't have this file be owned by the splunk user
when we create it, since the package hasn't been installed and the user
doens't exist yet. We'll let Puppet create it with the default
(probably root) and then let the Splunk package handle it from there.
This way Puppet and Splunk don't bicker over who should manage the
ownership.