radius-project / radius-project/docs
clarify reliance on bicep
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 26
- Forks
- 52
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
Overview of feature request
I get the impression that radius is tightly coupled to the bicep language. There's some mention of terraform in the docs too, but as a person just browsing the docs it's very difficult to determine if radius requires bicep or just supports it. We're not an azure shop, and we are reluctant to introduce yet another language/dsl to our stack.
Acceptance criteria
Some docs section description radius' relationship to bicep - whether it's required or not
Additional context
No response
Would you like to support us?
- Yes, I would like to support you
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 the existing Radius documentation references to Bicep and Terraform. Add a documentation section that clearly states whether Bicep is required or merely supported, and explain the role of Terraform where relevant. Done means a reader can determine whether Radius fits a non-Azure stack without further investigation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100