radius-project / radius-project/roadmap
Build-in OCI registry for Bicep extensions and recipes
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Overview of roadmap item
Today, Radius has several external prerequisites including a Kubernetes cluster, a Git repository for Terraform configurations, an OCI registry for Bicep recipes, and either Azure CR or a file share for Bicep extensions. This feature request is for building into Radius an OCI registry with the Bicep extension enhancements equivalent to Azure CR.
Related issues
Contributor guide
No contributing guide indexed for this repository
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 with the roadmap overview and the related issue, https://github.com/radius-project/radius/issues/9308. Determine the scope of an OCI registry built into Radius and the Bicep extension enhancements expected to match Azure CR. Done means the current external registry and file-share prerequisites are addressed by the built-in capability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100