You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
AidanCopeland
changed the title
Test against "null" to determine whether jq has returned a value
Protect against telemetry container restarts when config fields do not exist
Nov 15, 2021
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.
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.
AidanCopeland
changed the title
[dockers] Protect against telemetry container restarts when config fields do not exist
What I did
This PR fixes a bug in jq handling in the case where a lookup is made for a field that does not exist or is empty
Why I did it
Without this fix the telemetry container continually restarts until it hits the restart limit
How I did it
Provide additional checks against "null", being the value returned by jq if the field does not exist or is empty
How to verify it
Verified in internal testing with framewave
Description for the changelog
Fix handling of jq lookups for empty or non-existent fields
A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: Aidan Copeland acopeland@microsoft.com