Automated deployments can undo rollbacks or miss failure triggers
DevOps teams using automated deployments can struggle to keep a production rollback from being overwritten by auto-sync, or to trigger a rollback when deployment health alarms fire. The needed safeguards are not readily available in the workflows described: Argo CD users report multi-step rollback procedures, while CDK users requested access to CloudFormation rollback triggers and bake time. A focused tool could help, but it would need separate integrations for these deployment environments.
For devOps and platform engineering teams managing automated deployments. Mentioned from Nov 2019 to Apr 2024 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.5/10
- Frequency
- 5.8/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.
Users have to go through multiple steps, including creating PRs to disable auto-sync, just to perform a successful rollback without overwriting changes
This way we "try" (I say try as at this point its best we were able to do, so suggestion are welcome" ) to be more deterministic and not to sync over rollbacked production env
Build brief
See what to build and who will buy it
- 2 product ideas 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