Skip to content
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

docs: updates docs on gh-team-allowlist #2664

Merged
merged 1 commit into from
Nov 11, 2022

Conversation

dversoza
Copy link
Contributor

To better describe the flag about using the team name and not the slug, with practical examples.

To better describe the flag about using the team name and not the slug, with practical examples.
@dversoza dversoza requested a review from a team as a code owner November 11, 2022 15:12
@nitrocode nitrocode added the docs Documentation label Nov 11, 2022
@nitrocode nitrocode merged commit 74e522a into runatlantis:master Nov 11, 2022
@nitrocode
Copy link
Member

Thank you @dversoza !

@jamengual
Copy link
Contributor

jamengual commented Nov 11, 2022

I do not think this is correct, when I created this functionality if you did not pass the slug it would not find the team.

are you confident that this works?

@jamengual
Copy link
Contributor

it is possible that it worked but you might be allowing everyone

@dversoza dversoza deleted the patch-1 branch November 11, 2022 21:03
@dversoza
Copy link
Contributor Author

dversoza commented Nov 11, 2022

Hey @jamengual, in my case, using "Engineering Team:apply" instead of "engineering-team:apply" was the only way to make it work.

Using the slug returned an error response, and the permissions didn't work.

As it took me a long time, multiple back-and-forth tests, and code investigation to figure this out, I decided to add this note to the documentation to help newcomers.

--edit

As you mentioned, I also tested it, and it worked for preventing other teams from running plan or apply.

@nitrocode
Copy link
Member

We had a previous similar PR #2005 to mention it was a slug too. The PR here made it even more clear.

I wonder why a name would work but a slug wouldn't? It would be nice to support both.

krrrr38 pushed a commit to krrrr38/atlantis that referenced this pull request Dec 16, 2022
To better describe the flag about using the team name and not the slug, with practical examples.
@nitrocode nitrocode added this to the 0.21.0 milestone Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants