PowerShell / PowerShell/PowerShell-RFC
Idea: Release the SecretManagement and SecretStore modules with PowerShell
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 467
- Forks
- 140
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading this RFC and its 28-comment discussion, then trace how PowerShell defines its default installation footprint and assembles package contents. Done means the community has an agreed path for including the latest Microsoft.PowerShell.SecretManagement and Microsoft.PowerShell.SecretStore modules in PowerShell packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100