Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make secret vaults not require use of PowerShell #216

Open
SteveL-MSFT opened this issue Oct 9, 2023 · 1 comment
Open

Make secret vaults not require use of PowerShell #216

SteveL-MSFT opened this issue Oct 9, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@SteveL-MSFT
Copy link
Member

Summary of the new feature / enhancement

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

Proposed technical implementation details (optional)

No response

@JustinGrote
Copy link

JustinGrote commented 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
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

@SydneyhSmith SydneyhSmith added the enhancement New feature or request label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants