Infrastructure teams struggle to review and protect changes safely
Infrastructure and DevOps teams need to understand what a deployment will change and inspect what was applied, but the evidence describes missing or incomplete previews, hard-to-inspect plan details, and deployment histories without usable diffs. Terraform’s destroy protection can also make planning fail around protected resources, leading some operators to separate stateful resources into another deployment. A small product could improve review and history for a narrow set of tools, but it cannot change those tools’ underlying planning behavior.
For infrastructure engineers and DevOps teams managing declarative deployments. Mentioned from Nov 2015 to Nov 2023 on GitHub and Hacker News.
8 different people described this problem in 7 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.8/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.
This definitely is a critical tool to have before merging a change in git
I'm looking for this ability currently to prove that a release to staging was good, and I want the diff of what was applied last, but I can't find out how to get it other than roll back and then get the diff and roll forward again. which isn't really an option
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
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks