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

Set token to explicit content read permissions #2129

Merged
merged 2 commits into from
Jul 8, 2024

Conversation

davidcassany
Copy link
Contributor

No description provided.

@davidcassany davidcassany requested a review from a team as a code owner July 4, 2024 13:31
Comment on lines 24 to 25
permissions:
content: read
Copy link
Member

@pjbgf pjbgf Jul 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: It is also possible to set this at the highest level, and then just override the permissions on jobs that require more than content: read.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gonna set it at top level then, thanks

Signed-off-by: David Cassany <dcassany@suse.com>
Signed-off-by: David Cassany <dcassany@suse.com>
@davidcassany davidcassany enabled auto-merge (rebase) July 8, 2024 15:45
@davidcassany davidcassany merged commit 8b8ae12 into rancher:main Jul 8, 2024
28 checks passed
@davidcassany davidcassany deleted the restrict_token_permissions branch July 8, 2024 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants