You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 22, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 22, 2026. It is now read-only.
Make secret vaults not require use of PowerShell #216
Along with #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
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
Activity
JustinGrote commentedon Nov 20, 2023
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
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