Idea: Release the SecretManagement and SecretStore modules with PowerShell
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- release
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.
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.
- Dominant language
- PowerShell
- Stars
- 468
- Forks
- 143
- Avg merge
- 9m
- Merged PRs (30d)
- 1
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.
More from PowerShell/PowerShell-RFC
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/PowerShell-RFC#404 · 1 comment ·
-
PowerShell/PowerShell-RFC#407 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PowerShell/PowerShell-RFC#396 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
PowerShell/PowerShell-RFC#334 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PowerShell/PowerShell-RFC#270 · 4 reactions ·
All issues in PowerShell/PowerShell-RFC
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
nunomaduro/phpinsights#745 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
midnightntwrk/midnight-docs#1390 · 1 comment ·
-
area: install bug triage: reproducible
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
[bug] bl update: darwin-arm64 binary ships invalid ad-hoc signature, killed by macOS (Killed: 9) Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
modelstudioai/cli#223 ·
-
comp: build/pipeline type: bug version: current (v17+)
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
angular/angularfire#3766 ·