Fix: Replace unsupported repeated yaml anchors w/ merge #8
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
Duplicate YAML merge keys `(<<)` are now rejected from latest docker-compose spec. It fails with the following syntax error due to go/yaml/v3 update: ```sh $ docker-compose --project-name myidp -f docker-compose-ref.yml up -d parsing ./docker-compose-ref.yml: yaml: unmarshal errors: line 32: mapping key "<<" already defined at line 31 line 55: mapping key "<<" already defined at line 54 ``` "goyaml/v3 does not support repeated anchors (due to internal storage using << as key during parsing) but allows use of multi-values in anchors" See: - docker/compose#10411 (comment) - https://yaml.org/type/merge.html
RStaeber
approved these changes
May 5, 2023
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.
The use of duplicate YAML merge keys
(<<)is now rejected from latest docker-compose spec.It fails with the following syntax error due to go/yaml/v3 update:
References: