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.

Lies zunächst dieses RFC und seine Diskussion mit 28 Kommentaren, und verfolge dann, wie PowerShell seinen standardmäßigen Installationsumfang definiert und die Paketinhalte zusammenstellt. Als abgeschlossen gilt die Aufgabe, wenn sich die Community auf einen Weg geeinigt hat, die neuesten Module Microsoft.PowerShell.SecretManagement und Microsoft.PowerShell.SecretStore in PowerShell-Pakete aufzunehmen.