radius-project / radius-project/docs
Update GitHub Actions Guide to use OIDC auth instead of AZURE_CREDENTIALS
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 26
- Forks
- 52
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
This page: https://docs.radapp.io/guides/deploy-apps/howto-deploy/howto-deploy-cicd/ should be updated to use managed identities/OIDC instead of AZURE_CREDENTIALS and client secrets. See this guide for more information: https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure
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
Open the GitHub Actions deployment guide at the linked docs.radapp.io page and compare its authentication steps with the linked GitHub OIDC guide for Azure. Update the page to use managed identities/OIDC rather than AZURE_CREDENTIALS or client secrets, and consider the work done when the documented deployment flow is consistent with the current authentication approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100