Fix DD_TAGS format issues
#135
Merged
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
NouemanKHAL
added
the
changelog/Fixed
sarah-witt
reviewed
Oct 17, 2022
Co-authored-by: Sarah Witt <sarah.witt@datadoghq.com>
sarah-witt
approved these changes
Oct 19, 2022
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.
This PR fixes an issue where
DD_TAGSwould appear as a single (long) tag.Since the content of
DD_TAGSis already extracted inside theget_tags.pyscript (line 42), and injected into the agent config filedatadog.yaml.We should reset the env var as it's also being picked by the agent, and might cause some bugs in the tags format.