ci: use ephemeral tokens with the required permissions#249
Merged
Conversation
reakaleek
approved these changes
Sep 9, 2024
Member
Author
|
The CLA checker will cause some disruptions - I'm working on it with the relevant CLA owners. For now, I'll keep this draft to avoid surprises. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Use https://github.com/tibdex/github-app-token to generate ephemeral tokens so we can automate:
Why
This is the alternative to moving away from finer-grained GitHub tokens and reducing the cumbersome of rotating them as we do nowadays.
Implementaiton details
We have used the same GitHub action in other places. I'm just trying the
permissionsflag to avoid using other permissions that require least-permissive access.Release automation uses the ephemeral GitHub token generated by the GitHub action itself.