-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve stability of the CAPI metadata tags collection feature #148
Improve stability of the CAPI metadata tags collection feature #148
Conversation
… cf restart scenarios
…gs from being overriden
This reverts commit b820a5b.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, left some comments!
# verify that check_datadog exited successfully | ||
if [ ${exit_code} -ne 0 ]; then | ||
log_error "could not find agent, aborting update script!" | ||
exit ${exit_code} | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, I think we should still try running the update script. Maybe the agent was killed in between runs of the script. But if we don't do this, then we should confirm the trace agent isn't running before exiting since we don't want to be in a state with the trace agent running but not the agent.
…ction file, cleanup code, remove ruby scripts
… the lockfile to matcht the script name
What does this PR do?
SUPPRESS_DD_AGENT_OUTPUT
behaviour and logs redirection.ImportError: No module named site
on thecreate_logs_config
python script by switching to Ruby.update_tags.rb
script.update_agent_config.sh
script.Review checklist (to be filled by reviewers)
changelog/
label attached. If applicable it should have thebackward-incompatible
label attached.do-not-merge/
label attached.kind/
andseverity/
labels attached at least.