Idea: Release the SecretManagement and SecretStore modules with PowerShell

Summary of the new feature / enhancement

As a user, I have a consistent need to manage secure strings without exposing them in scripts and other automation artifacts. To rely on this capability in PowerShell, I need it to always be available without the need to add the installation to every new project, or finding workarounds to add it in the tools of my choice that run PowerShell.

Proposed technical implementation details (optional)

This experience would align with other modules that are released with the "default" installation footprint of PowerShell. There is no need to merge the source repo's or manage the projects as a single entity. When the PowerShell packages are built, the latest Microsoft.PowerShell.SecretManagement and Microsoft.PowerShell.SecretStore modules would be included.

Commencez par lire ce RFC et sa discussion de 28 commentaires, puis retracez la manière dont PowerShell définit son empreinte d’installation par défaut et assemble le contenu des packages. Le travail sera considéré comme terminé lorsque la communauté aura convenu d’une méthode pour inclure les derniers modules Microsoft.PowerShell.SecretManagement et Microsoft.PowerShell.SecretStore dans les packages PowerShell.