Add ability to specify --scope to winget upgrade

[o-l-a-v]

Description of the new feature / enhancement

Add a switch for scope/context with winget upgrade, both for listing upgrades (specifying no apps), and when upgrading a specific app.

Example use case

List upgradeable apps

• A user without admin permissions wants to check what apps can be upgraded, thus listing system context apps makes no sense.
  • winget upgrade --scope user
• Running winget in system context, thus upgrading user context apps makes no sense.
  • winget upgrade --scope machine

Upgrade app

• Teams is installed with the system wide MSI installer, but user without admin permissions wants to upgrade Teams in user context.

  • winget upgrade --exact --id Microsoft.Teams --scope user

• A user without admin permissions wants to upgrade all user context apps.

  • winget upgrade --all --scope user

Proposed technical implementation details

Detection rules should say something about scope/context. So should the manifest too.

Edit 221221

• Changed from --context to --scope for consistency with winget install.

[cjwijtmans]

The existing flag would be --scope not --context. Not sure if consistency would be prefered or avoiding confusion would be prefered. Personally i prefer consistency 🤷🏼‍♂️

[o-l-a-v]

I agree, --scope for consistency.

[eabase]

Also very useful if the scope is shown when listing.

I.e. provide the functionality for added column with scope.

# Adding scope column in output
winget list --scope

# only showing items with machine scope
winget list --scope machine

[Trenly]

[Policy] Command-Upgrade

[eabase]

@Trenly

Sorry, I don't understand your answer/comment.

[Trenly]

@Trenly

Sorry, I don't understand your answer/comment.

I was simply applying a label

[github-account1111]

Teams is installed with the system wide MSI installer, but user without admin permissions wants to upgrade Teams in user context.

• winget upgrade --exact --id Microsoft.Teams --scope user

What is supposed to happen in this scenario? Should winget install the user version of Teams (alongside the outdated system-wide one)?

What's the current behavior when a program is installed in both scopes, and `winget upgrade --id is run?

[o-l-a-v]

Teams system wide installer is, at least used to be, a special one. It installs Teams in user context for all users that log in on that device and don't have Teams installed already. Thus in this scenario I'm pretty sure using WinGet to update Teams in user context would woek just fine.

[github-account1111]

Okay, you should've probably specified that in the issue because that's definitely not common knowledge or how most programs behave. Most programs, when installed with a system-wide installer, are installed system-wide, i.e. in Program Files, not just for all users.

So my question still stands.