radius-project / radius-project/roadmap
Ability to configure which Recipe drivers are enabled
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
We should make the set of recipe drivers configurable either as part of a Radius installation or as part of a Radius environment. A recipe driver is the component that enables a specific technology for use in recipes. eg: the Terraform driver supports Terraform, and the Bicep driver supports Bicep. We will expand and generalize the set of possible drivers over time meaning that additional technologies will be added.
For compliance reasons, organizations may want to limit the set of drivers based on many different requirements. The scope of this issue is to determine the mechanism for configuration as well as the defaults.
Related issues
### Related issues
- [ ] https://github.com/radius-project/radius/issues/6915
Additional context
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
Review related issue #6915 first, then compare the installation and environment scopes described here. Define the configuration mechanism and defaults for enabling recipe drivers, and confirm the result supports compliance-driven restrictions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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