-
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: add ignore-vcs-status-names (github only) #4978
feat: add ignore-vcs-status-names (github only) #4978
Conversation
`other-vcs-status-names-to-ignore` is a comma-separated list of atlantis vcs status names that will be ignored when deciding if the PR is mergeable or not. This PR is a proposal to solve [runatlantis#2848](runatlantis#2848) for github client.
interesting proposition. vcs-status-to-ignore:
- name1
- name2
- etc |
@jamengual thanks for the feedback, why do you think it is much better? I would actually imagine that having |
Because we have a trillion flags, and we want to avoid having more that is the main reason, plus if is moved there then you can have different repos regexes with different statuses. |
@jamengual I've been looking at the code and I believe it's gonna be pretty complex to do
because the FetchPullStatus is not called at the repo config level. It's basically a sort of boolean ("has been approved" and "is mergeable", no conditions) Also, I am struggling to understand the benefit of having different repos regexes with different statuses. Simply put, #2848 is basically a bug where multiple atlantis instances with different vcs status name conflict with each other and forbid the apply when Wdyt? |
Sorry, this is a standard ask we ask everyone. |
Small nitpick, |
FYI, I've tested this change on my environment (Dev, Staging, prod) with |
Hey @jamengual, do you know when we can get this PR reviewed? It’s been running fine on 20 of my atlantis servers for the past 2 weeks and working as expected. I’d like to deploy it to my other 50 ones. But I would prefer to use your upstream version instead, versus my own docker image. Thanks. |
@X-Guardian thx, this is done. |
The documentation needs updating to add this new flag here: https://github.com/runatlantis/atlantis/blob/main/runatlantis.io/docs/server-configuration.md |
@X-Guardian done as well. Thanks. |
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.
Nearly there @bakayolo. Just need to get the docs refined.
@X-Guardian thanks. Done.
The description is actually right. This PR only ignore vcs status names such as |
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.
Thanks @bakayolo. Just a couple of small refinements and we are good to merge.
Co-authored-by: Simon Heather <32168619+X-Guardian@users.noreply.github.com> Signed-off-by: bakayolo <benjamin.apprederisse@gmail.com>
Co-authored-by: Simon Heather <32168619+X-Guardian@users.noreply.github.com> Signed-off-by: bakayolo <benjamin.apprederisse@gmail.com>
Thanks @X-Guardian ! Should be good! 👍 |
@bakayolo, can you resolve the merge conflicts? |
Signed-off-by: bakayolo <benjamin.apprederisse@gmail.com>
@X-Guardian all good, thanks! |
Signed-off-by: X-Guardian <simonheather99@gmail.com>
Thanks for this @bakayolo. You can test it using one of these container images: dev-alpine-841f7b4 or dev-debian-841f7b4 |
Nice! Thanks! |
what
Comma separated list of VCS status names from other atlantis services.
When
gh-allow-mergeable-bypass-apply
is true, will ignore status checks (e.g.status1/plan
,status1/apply
,status2/plan
,status2/apply
) from other atlantis services when checking if the PR is mergeable.Only for Github but can be extended to other VCS in the future.
why
This PR is a proposal to close #2848
tests
I have only runmake test
but planning on testing in my own environment if the proposal is accepted.Tested with
make test
and on my environment withbappr/atlantis:cud-ignore-vcs-status-names-ca1171e0dd174edbbd63f8f6ae560caa6af4c0c7-0
.references
closes #2848