search

PowerShell / SecretManagement

PowerShell module to consistent usage of secrets through different extension vaults
MIT License
317 stars 46 forks source link

Make secret vaults not require use of PowerShell #216

Open SteveL-MSFT opened 8 months ago

SteveL-MSFT commented 8 months ago

Summary of the new feature / enhancement

Along with https://github.com/PowerShell/SecretManagement/issues/211 we should make it so that vault authors don't need to use PowerShell at all so this library becomes the abstraction layer for .NET secrets

Proposed technical implementation details (optional)

No response

JustinGrote commented 7 months ago

The only command that doesn't use built-in types is Get-SecretInfo.

The current 0.9.3 version of the nuget package appears to have all the current surface area (metadata being the big one) https://www.nuget.org/packages/Microsoft.PowerShell.SecretManagement.Library/0.9.1 image

So at least for PS7+ using this module should assemblyredirect fine to the newer one that comes in the PS module. PS5 will need a binding redirected added though.

The nuget package should still also be updated to 1.1.2 and have vault authors instructed to use it with PrivateAssets=true, and the secretmanagementmodule itself should implement the binding redirect