-
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
fix: Check user permissions on autoplan #3742
Conversation
I think the tests need to be updated since they are failing on CreateComment |
Hey @GenPage. Thanks for taking a look. I've updated the failing tests, and changed what I assume is a typo of conftest. |
Hi @GenPage , are we able to remove the "waiting-on-response" label for this one? Please let me know if there is anything I can do to help progress. |
Looks like it is failing now on installing Alpine packages? I'm not entirely sure if this is related to my change. |
Sorry to keep chasing up @jamengual, would this now need the "waiting-on-review" label? |
/cherry-pick release-0.26 |
/cherry-pick release-0.26 |
* Check user permissions on autoplan --------- Co-authored-by: PePe Amengual <[email protected]>
* Check user permissions on autoplan --------- Co-authored-by: PePe Amengual <[email protected]>
what
This change enforces the team permissions on autoplans. Currently Atlantis will autoplan any PR when a team is configured.
why
The current behavior is a security risk for us. We have a large number of teams sharing the same GitHub org. We want to encourage inner-sourcing and collaboration by allowing forks from other teams within the orgs, but these PRs we don't trust until they have been reviewed by a team member that owns the project.
tests
We having been running this for a number of months internally on a small handful of repositories. This was the only vulnerability we could find when using Atlantis team permissions with our team and trust model on GitHub.
references