Cloud infrastructure teams duplicate configuration across IaC templates
Infrastructure developers report copying the same settings, values, and expressions across templates because their configuration workflows lack convenient reusable blocks, constants, or aliases. That repetition makes updates easy to miss and can lead to inconsistent configurations; workarounds such as comments, template generation, and custom wrappers add effort. The signals are historical feature requests, so current support and demand should be checked before building.
For cloud infrastructure developers. Mentioned from Sep 2016 to Nov 2023 on GitHub.
8 different people described this problem in 6 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 5.5/10
- Frequency
- 7.9/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Advantages: - less copy & paste - less errors when changing a thing (think subnet lists) in one place, but forget to in another - reusability of computed values (Fn::Join, Fn::Sub, Fn::Cidr)
I don't want to have to copy and paste that !Join statement throughout my template. Copy-ing and pasting is almost always bad. (e.g. what happens when I modify one instance of that !Join expression and I forget to change the others.)
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 5 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks