"atlantis yolo"

[ActuallyTrent]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

• [ ] I'd be willing to implement this feature (contributing guide)

Describe the user story

As an engineer, I would like to have fresh authentication tokens when running apply, but I have to re-run atlantis plan to obtain them.

As a security-minded engineer, I do not want to extend token lifetimes, because that increases risk.

As an engineer, I would prefer to not re-run a plan that takes a long time and wait for the plan output to run an atlantis apply as I would like to context switch and work on something else, but if I context switch I may be late to an atlantis apply.

As an engineer, I would prefer to not re-run a plan for manual review if I do not need to, as I know nothing has changed in the underlying Terraform state and I received an appropriate review from my team.

As an engineer, I would like a self-describing and clear mechanism for knowingly circumventing safety features.

Describe the solution you'd like

A command/flag (atlantis yolo, atlantis plan -apply, atlantis apply -yolo, etc) that allows atlantis to plan and immediately apply the plan, without requiring manual interactions between the plan and apply stages. Ideally, this command would fail if code changes occur upstream (main branch, for example) in the current project. The command should also respect PR locks and other safety features. Additionally, it would be nice if this diff'd the new plan against the last plan and only applied if there are no changes.

Describe the drawbacks of your solution

Errors may occur if the underlying Terraform state changes.

Users need to be more aware of activity in their repositories and environments.

[ahammond]

I think yeet might be a better name for it. :)