Fix YAML parse error in service-secret.yaml template#54
Merged
Conversation
…ment before data key Co-authored-by: dkrizic <1181349+dkrizic@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix helm chart upgrade error for frontend feature
Fix YAML parse error in service-secret.yaml template
Jan 26, 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
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.
Helm deployment was failing with "did not find expected key" error on line 13 of
service-secret.yaml.Change
Moved template variable assignment before the
data:key. YAML requires mapping keys to be immediately followed by values or child key-value pairs, not non-output-producing template directives.Before:
After:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.