[3.x] Fix YAML date coercion - #442
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Backport of #441. Unquoted date-shaped scalars such as an IAM policy Version were parsed into Date objects by the YAML schema and serialized into compiled templates as ISO 8601 strings, a date behind a file variable failed the whole configuration resolution, and the plugin-facing file reader and external $ref loads did not use the CloudFormation schema at all. Quoted and !!str values were never affected.
This carries the original commit from @mklenbw plus the review follow-ups from the 4.x pull request: the timestamp type stays available as an explicit !!timestamp tag, and the same schema now applies on every YAML parse path.