Cloudformation specific YAML encode function to validate template before using `aws_cloudformation_stack`

[nitrocode]

Description

Problem is that the cloudformation stacks sometimes do not follow the correct spacing or yaml spec when it is modified. We find out upon apply instead of during the init/plan phase.

We can use something like cfn-lint or other tools to catch this but it would be nice to have it in native in the provider so we do not have to use external tools.

For example, if we want to make sure the json or yaml is correct, we can do something like this before we create the resources that depend on these templates.

locals {
  yaml_object = yamldecode(file("${path.module}/stack.yaml"))
  json_object = jsondecode(file("${path.module}/stack.json"))
}

---

I tried this and received an error because the cloudformation yaml contains some cloudformation-isms that are not compliant with the YAML spec.

locals {
  raw_file    = file("${path.module}/cfstack.yaml")
  yaml_object = yamldecode(local.raw_file)
}

If there was a provider function to do this, that would make it much easier to turn this into a parsable object.

e.g. cfdecode

locals {
  raw_file    = file("${path.module}/cfstack.yaml")
  yaml_object = provider::aws::cfdecode(local.raw_file)
}

Affected Resource(s) or Data Source(s)

• aws_cloudformation_stack

Potential Terraform Configuration

See above

References

N/A

Would you like to implement the enhancement?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.