Infrastructure teams lack safe automation for plan and apply workflows
Teams using Atlantis and OpenTofu want tighter control over infrastructure changes, but their workflows can allow changes to merge without a successful apply, require people to approve and apply no-op plans, or lack an easy way to avoid refreshing unchanged resources. The resulting manual work and proposed state-manipulation workarounds make routine infrastructure changes harder to manage. These are related workflow problems, but solving refresh behavior safely is substantially more technically sensitive than adding pull-request controls.
For infrastructure engineers and platform teams. Mentioned from Jun 2022 to Jun 2024 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 7.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
We would love something along these lines as feature, as this is something that happens on a regular basis with engineers new to our team, or for engineers from outside our organisation
In this case, an approver will have to come along, approve each request, and apply the change (which makes no write API calls to AWS, but will update the state file with the new provider/module version numbers)
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks