microsoft / microsoft/winget-pkgs
[Update Request]: Add user scope installer to Amazon.AWSCLI package
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 616
Description
### What type of update are you requesting?
A new locale, architecture, or installer type of an existing version
### Current Package Identifier
Amazon.AWSCLI
### Package Version
2.35.9
### Please describe the changes you would like to see
The AWS CLI now provides a user scope installer for Windows on top of the existing system scope one. Please update the winget installer to support `--scope user` installations as the default and `--scope system` as an option.
System-wide installer: https://awscli.amazonaws.com/AWSCLIV2.msi
Per-user installer: https://awscli.amazonaws.com/AWSCLIV2-User.msi
The [Documentation](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html) has now been updated with per-user installation instructions.
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 locating the Amazon.AWSCLI package manifest in winget-pkgs and reviewing how its current installer scope and URLs are represented. Compare the manifest schema and nearby package examples for user and system scope options. Done means the user installer is the default, the system installer remains selectable, and the manifest validates successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100