CloudFormation users hit friction working with YAML
Some Amplify developers have to convert CloudFormation YAML to JSON in their workflow, while others find JSON templates difficult to navigate. AWS CLI users also report that parameter files do not accept YAML even though templates do. The evidence includes a pre-push conversion hook as a workaround; a separate request about a missing CloudFormation resource is related to AWS infrastructure but is a different problem.
For AWS infrastructure developers. Mentioned from Feb 2017 to Jun 2022 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I worked around this by adding a pre-push hook that converts my cloudformation yaml to json. Ugly and far from perfect but it works š¤·
I would really appreciate this, as Iām finding my json cf templates very difficult to navigate :/
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks