Handling ElevationRequirement enum in context with scope?

[byjrack]

So if you scope user and ElevationRequirement is not elevationProhibited you could get prompts for elevation that a user can't complete via UAC. Reason this matters is we are putting these in Company Portal (CP) and had tried to use user scope so updates could be completed by the user vs going back to the CP install.

If the install is called --scope user and the manifest includes an element to support that, but elevatesSelf and elevationRequired the user may not be able to complete successfully. Install doesn't look to have a flag to further filter elevation needs (though I have missed functionality before) and didn't know if someone has a trick. I would rather have no manifest found if i could have another elevation arg or a more freeform --filter of attributes in the manifest using jsonpath type model.

I get the need to decouple scope and elevation for some compatibility needs like Docker Desktop could install most under the Packages/Programs root in the User, but there are some helper daemons that need elevated rights. If users can't UAC though I am trying to figure out ways to keep winget working well for things that don't need elevation surfaced via CP for convenience. And maybe the Intune support could help reduce some of these corner cases.