Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Spec] Windows Package Manager Repair functionality Design spec #3943

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

Madhusudhan-MSFT
Copy link
Contributor

@Madhusudhan-MSFT Madhusudhan-MSFT commented Dec 1, 2023

This PR introduces the initial design specification for the repair functionality in Windows Package Manager. This new experimental feature will allow users to repair installed packages using the Windows Package Manager.

Related to:


Microsoft Reviewers: Open in CodeFlow

This commit introduces the initial design specification for the repair functionality in Windows Package Manager. This new feature will allow users to repair installed packages using the Windows Package Manager.

This comment has been minimized.

This comment has been minimized.

@denelon
Copy link
Contributor

denelon commented Dec 1, 2023

Comments/Concerns:

@ImJoakim
@ItzLevvie
@jedieaston
@KaranKad
@mdanish-kh
@OfficialEsco
@quhxl
@russellbanks
@Trenly

This commit fixes the spelling-bot report by adding the expected entries to the expect.txt file.
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
doc/specs/#148 - Repair Support.md Outdated Show resolved Hide resolved
- the repair command will not work if the installer does not have a custom repair switch specified in the YAML manifest file.
- the repair command will not work if the installed Burn/Exe installer type doesn't correlated to the remote installer type that has a custom repair switch specified in the YAML manifest file.

## Future considerations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we handle elevation requirements when the modification requirement is different from the install requirement? What about when a package is installed in machine scope and a non-elevated session is attempting the modify?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should explore real-world scenarios where the requirements for modifying elevation differ from those for installation.
Currently, our design assumes that the requirements for modification elevation align with those for installation, similar to uninstallation.

The expectation/assumption for "when a non-elevated session attempts to modify a package installed for machine scope", the installer will prompt for elevation appears to be the case with some sample runs. However, when a package installed for user scope is run in an admin context, the repair operation is restricted due to possible security risks.

doc/specs/#148 - Repair Support.md Show resolved Hide resolved
@denelon denelon changed the title Windows Package Manager Repair functionality Design spec [Spec] Windows Package Manager Repair functionality Design spec Dec 6, 2023

This comment has been minimized.

@Madhusudhan-MSFT Madhusudhan-MSFT marked this pull request as ready for review January 8, 2024 20:24
@Madhusudhan-MSFT Madhusudhan-MSFT requested a review from a team as a code owner January 8, 2024 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants