microsoft / microsoft/winget-cli-restsource
Custom URL and Key
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 317
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Description of the new feature / enhancement
We want to be able to support a REST source being hosted on infrastructure other than just Azure.
This would not impact the reference implementation, but additional improvements need to be made to have the PowerShell cmdlets communicate with any REST implementation. Note: the New-WinGetSource will continue to support only Azure, but the other cmdlets will be using the "management" REST endpoints and not connecting with Azure resources directly.
Proposed technical implementation details
No response
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 the PowerShell cmdlets and the New-WinGetSource entry point, then trace how the management REST endpoints are used. Done means the other cmdlets can communicate with a REST implementation hosted outside Azure while New-WinGetSource remains Azure-only.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100