Flatten release failure annotations for Datadog - #121
Merged
Merged
Conversation
Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
gontzess
marked this pull request as ready for review
September 18, 2026 18:42
jugonzalez12
approved these changes
Sep 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 shared release failure notification interpolates multi-line annotations into the masci/datadog events YAML block scalar, causing YAML parsing to fail and suppressing the Datadog event. The registry incident surfaced the latent defect.\n\nThis flattens collected annotations to one lossless line before the unchanged declarative send step. It affects every connector CI consuming release.yaml through v2/v3/v4; the fix must be included in those tags (or a replacement tag) to take effect.\n\nVerification: a two-line annotation fixture produces zero output newlines after the same tr/sed transform, and a local PyYAML render of the events block parses successfully.\n\nA separate follow-up can enrich the annotation with the response body; this PR intentionally does not.