Atlantis teams lack reliable controls for infrastructure plan lifecycles
Teams using Atlantis can be blocked by stale plans that need manual cleanup, or wait for an irrelevant running plan to finish before they can proceed. They also want to cancel and rerun plans without triggering downstream tooling from an outdated result. The signals describe related gaps in plan expiration, cancellation, and rerun behavior; they date from 2018–2019, so current Atlantis capabilities need checking before building.
For infrastructure teams using Atlantis. Mentioned from Sep 2018 to Aug 2019 on GitHub.
3 different people described this problem in 2 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.0/10
- Frequency
- 5.0/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.
This helps with workflows where you have many folks working on the same repo: you get a plan, apply it within 15 min or else it times out and you need to run plan again. This would let other users work on the plan without having to discard the plan manually from the atlantis UI
Personally I'd prefer an abort so that other tooling waiting on ✅doesn't start up (race condition)
Build brief
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