-
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
feature request: apply on merge #36
Comments
Comment by @robertlabrie piling on my own request, plan on push would be dandy as well :) |
Comment by @lkysow Thanks for the ticket! The main reason we do apply on comment is that often there are errors when you run That being said, I don't think there's a reason we couldn't also support a final apply on merge for any plans that are outstanding. What do you think @anubhavmishra? For plan on push, we definitely agree this is needed. I created #165 to track this separately. |
I've decided against doing this for now. Although there are valid use-cases for applying after merge, I'd like to focus on the most common use-cases where applying on the pull request and locking the directory until the pull request is merged works well. |
Issue by @robertlabrie
Thursday Oct 19, 2017 at 12:21 GMT
Migrated from hootsuite/atlantis#162
Why was it migrated?
Would be great if merging a PR triggered a
terraform apply
The text was updated successfully, but these errors were encountered: