Support for YAML v1.1 and 1.2 #160
Open
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
Currently CF validates YAMLs according to their schema at version 1; That being said, it forces all YAML features to stick to v1, which is old and lacks many features (like variables)
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.
TLDR
Adding support for YAML v1.1 and v1.2
Desc
currently, CF validates its own YAML schema at version 1.0, but by stating
version: 1.0at the top of the YAML users are bound to YAML version of1.0, which is >6 years old.My change allows to YAML 1.1 and 1.2 to be used with the CF system while still conforming the internal YAML struct to CF's restrictions
This is wrt to #159