radius-project / radius-project/radius
Use a GitHub App token in all Radius workflows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 137
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 110
Description
We periodically run into workflow authentication issues due to PAT expiry.
We should move to using App tokens which does not have a maintenence overhead.
https://github.com/radius-project/radius/pull/8392 has the changes. However, with these changes workflow fail and rad init, since they cannot pull images from ghcr. We should identify the right permissions for the App to get past the issues.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR 8392 and the Radius workflows it changes, then trace the authentication used by workflow runs and rad init when pulling images from GHCR. Identify the GitHub App permissions needed for those pulls and confirm that all workflows and rad init succeed without PAT authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- authentication, ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100