microsoft / microsoft/winget-cli
Add `securityContext: elevated` during configuration export
Open
Nobody has claimed this yet.
Command-Configure
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
When I export my configuration, several WinGet packages trigger UAC. The Package resource should be robust enough to include the necessary context for elevation in the configuration file.
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
No files or tests are named. Start by tracing the configuration export flow and the Package resource in the WinGet CLI, then determine where exported package entries are assembled. Done means exported configurations include securityContext: elevated where needed so the affected packages no longer trigger UAC during application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100