radius-project / radius-project/radius
Feature request: support common package managers for Radius CLI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 137
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 110
Description
Overview of feature request
Today, the Radius CLI is installed via an installation script. The script further installs components by executing rad bicep download. Coming soon will be another binary manifest-to-bicep-extension. This feature request is to support package managers for CLI installation:
p0 HomeBrew
p0 WinGet
p1 apt
p2 rpm
Acceptance criteria
No response
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 with deploy/install.sh and the Radius CLI installation flow, including the rad bicep download step. Determine the packaging and distribution requirements for Homebrew, WinGet, apt, and rpm, then confirm the scope and acceptance criteria; done means the prioritized package managers can install the CLI and its required components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, shell
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100