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.

Empieza leyendo este RFC y su discusión de 28 comentarios; después, sigue cómo PowerShell define su huella de instalación predeterminada y ensambla el contenido de los paquetes. Se considerará terminado cuando la comunidad haya acordado una forma de incluir los módulos más recientes Microsoft.PowerShell.SecretManagement y Microsoft.PowerShell.SecretStore en los paquetes de PowerShell.