-
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
feat: disable autoplan label #3649
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
It would be nice to have more test coverage for the VCS implementations.
Because the other clients can be implemented on an "On Demand" bases, this PR can be merged without these implementations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@jamengual @GenPage @chenrui333 could you take a look at this PR? We'd love to have the feature included in the next release. |
I found this because I also need this feature. My use case is that I have a pull request created via automation and need to include terraform args to replace some resources. ie. |
I will be taking a look over the weekend. |
# Conflicts: # server/events/command_runner.go # server/user_config.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, good tests. Thank you for the feature contribution
Hi @ghaiszaher, just wanted to say thankyou for coming up with this feature, as it has made our apply/rebase/merge process much quicker on our infra repo! |
We've had |
a lot of people use them and they are quite happy since it fits their
development workflow and others like you prefer not to use them, it is a
choice but not a bottleneck.
…On Thu, Jan 11, 2024, 9:15 a.m. Brandon Fryslie ***@***.***> wrote:
We've had plan locks turned off entirely (both Atlantis and Terraform) in
our dev environment and there seem to be 0 consequences. It's been months.
They were a massive bottleneck.
—
Reply to this email directly, view it on GitHub
<#3649 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ3ERF42HMWQF3JDN2VDX3YN7JXVAVCNFSM6AAAAAA3FNQCASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBXGAZTOMJTGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I've sometimes wondered if removing the locks is a working solution. Good to know that some people have disabled it and it's working for them. I would hope that if you do not run into edge cases then maybe we can disable locking in atlantis by default and turn it on with a flag when users want it. |
@brandon-fryslie please see #2876 |
* feat: disable autoplan label * documentation * revert unrelated change * fix property * gitlab and github * dd more test * small fixes * add tests for github and gitlab clients * fix: remove unrelated comments * fmt --------- Co-authored-by: PePe Amengual <[email protected]>
* feat: disable autoplan label * documentation * revert unrelated change * fix property * gitlab and github * dd more test * small fixes * add tests for github and gitlab clients * fix: remove unrelated comments * fmt --------- Co-authored-by: PePe Amengual <[email protected]>
what
--disable-autoplan-label=<string>
ATLANTIS_DISABLE_AUTOPLAN_LABEL=<string>
--disable-autoplan
flag is set totrue
, the new flag--disable-autoplan-label
has no effect--disable-autoplan-label
is unset or if it's an empty string, it will have no effectwhy
We encounter this especially in a large repository used by many developers. It gets hard to manage the lock queue so we use an external bot to manage the queue for us. Only in certain pull requests, we don't want the autoplan feature to kick in.
tests
Tested with a Github pull request and environment variable
ATLANTIS_DISABLE_AUTOPLAN_LABEL=no-autoplan
.references