-
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
Disable automatic plan server flag #425
Comments
Hi Benjamin, this will have to be implemented when #47 is done. It's not sustainable to create global server flags for all possible repo configuration. |
Unfortunately I don't think it makes sense to add this to the Atlantis core. In all other uses cases I'm aware of, there is no need to disable autoplanning at the server level. Since this isn't as popular a use-case I don't think it's worth the added complexity. |
👍 Thanks for the consideration. |
Hi @lkysow, We have a configuration with hundreds of workspaces in a repo. We would not want hundreds of plans running when we are just trying to deploy/work from a new workspace. We could really use a flag for this. |
@bam0382 you could list each workspace in the |
Thank you @lkysow. Could we reverse that and white list instead of black list? |
Once you create an
and version: 3
projects:
- dir: dir1 Then changes in |
bash-4.4# atlantis version
atlantis 0.4.13
Issue:
I'd like to be able to disable automatic planning as a server flag.
I see this option if using atlantis.yaml files.
https://www.runatlantis.io/docs/atlantis-yaml-reference.html#autoplan
In my opinion, every option that is exposed for individual repos should be able to set as a default server wide. The local atlantis.yaml files could still override the server default if desired.
Why?:
The reason behind this is that we often (not always) use terraform workspaces and the initial plan fails because default workspace errors (intentionally) due to the workspace not being set. Our terraform looks up the workspace and uses that as a map key to cause this intentional error.
The text was updated successfully, but these errors were encountered: