-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce an option to lock/prevent applies. #680
Comments
If you have a load balancer in front you could point it at wrong ports? |
I could also delete the webhook, but it would be nice to have a built-in feature in the atlantis server, because then atlantis could deliver custom messages as responses to Example atlantis response: |
This and #729 could be the same thing yes? |
I have the same question/requirement. What should I do if I want to use altantis only for planning and not apply? |
You could create a default workflow whose |
is there a timeline for this to be implemented/released? is anyone working on this at all? if not, can I (or one of my team) raise a PR to implement this? Basically the feature as I see it is introducing an explicit set of people who are allowed to apply or a set of people whose approval is required to apply. |
This ticket is not about having a specific set of appliers. This is about having a "Freeze-all-operations" switch that prevents all further Atlantis actions. #308 is what you're asking about. If you want to talk about implementation please use that ticket. And also note that this can be accomplished right now with a custom workflow. |
Just in case somebody is stumbling across this as well. The feature has been implemented in Atlantis OSS: #1230 |
Currently, if there is an emergency situation, I can't think of a way to prevent atlantis from running
atlantis apply
aside from killing the atlantis server which could result in state corruption for any ongoing jobs.Any ideas? Has anyone run into this?
The text was updated successfully, but these errors were encountered: