Create newrelic user to fix java and ruby agent installation #334
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.
As described in #313, java and ruby agent installation fails because newrelic user does not exist. The user is created when you include
newrelic::server_monitor_agent
recipe but:a. you do not want to have server monitor agent installed in some cases
b. it is being deprecated in favor of New Relic Infrastructure. The later does not create a separate user and runs as root.
To solve this, I attempt to create the user unless it already exist.