microsoft / microsoft/vscode-python-environments
User Approval Flow for Package Installation
Abierto
Nadie ha tomado este issue todavía.
feature-request
needs spike
- Lenguaje dominante
- TypeScript
- Estrellas
- 138
- Forks
- 62
- Merge medio
- 1 d 4 h
- PR fusionados (30 d)
- 35
Descripción
Since this extension handles package installs, it should also correct communicate to the user about package installs and get user consent. The flow around package installs, user approval, when to allow background installs etc should be discussed and a plan outlined.
Security:
This is an important part of the user trust boundary as we should only have extensions install packages that have user consent. There could be different categories, trusted extensions that are allowed to install packages and untrusted extensions that need user consent to install.
Scenarios:
- extension wants to install a package, it is not a pre-approved extension to install packages
- extension wants to install a package, it is a pre-approved extension to install packages
- user wants to reduce notifications and select to have packages installed in the background for a given extension
- user wants to add, revoke, or edit which extensions can install / remove packages in a given workspace
- user wants to add, revoke, or edit which extensions can install / remove packages at a user or more global level
- user wants to accept installing a package without consenting to approve this extension going forward
Questions:
- How do we make sure users are in control of the package installs while not making the experience too noisy?
- Are there any extensions (like ones published by microsoft) that do not need to be prompted for the user to accept maybe only notified?
- Do we still notify users on package install even if the installer is a pre-approved extension? Do users want to be notified every time?
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.