fix(aws): Handle YAML cloudformation template bodies #10826
Merged
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.
This fixes an issue with the new
aws_cloudformation_stack_templates
table, where it seems like the AWS API can return YAML as well as JSON for the template body, so we cannot assume it to be JSON.This was a tricky one to fix in a backwards-compatible way, however, because the column is now of JSON type. My solution here is to:
template_body
columntemplate_body_text