Feature Request: Set-SecretInfo should take pipeline input

PowerShell / SecretManagement

PowerShell module to consistent usage of secrets through different extension vaults

MIT License

328 stars 46 forks source link

Closed jdhitsolutions closed 3 years ago

jdhitsolutions commented 3 years ago

It is a common PowerShell practice to run a Get command and pipe to a Set command. I would expect to be able to run a command like this:

get-secretinfo -Vault $vault -Name foo* | Set-SecretInfo -Metadata $meta

But the Name and Vault parameters on Set-SecretInfo don't accept pipeline input. I can't imagine why they shouldn't.

PaulHigin commented 3 years ago

Yes, this support can be added.

PaulHigin commented 3 years ago

Implemented in v1.1.0-preview