It's best practice for a module to have the same prefix for every cmdlet in a module so that users know that a cmdlet comes from a module... Or use a prefix that gives context to the user on what they are doing.
Set-DefaultVault doesn't have the prefix that the others do and I worry that it could stomp on an existing cmdlet since Vault is fairly overloaded in the key store space.
This cmdlet should either be Set-SecretDefaultVault or Set-SecretVaultDefault.
My vote to the latter (Set-SecretVaultDefault).
It feels more aligned with other vault operations (Test-SecretVault / Register-SecretVault / UnregisterSecretVault)
It's best practice for a module to have the same prefix for every cmdlet in a module so that users know that a cmdlet comes from a module... Or use a prefix that gives context to the user on what they are doing.
Set-DefaultVault
doesn't have the prefix that the others do and I worry that it could stomp on an existing cmdlet sinceVault
is fairly overloaded in the key store space.This cmdlet should either be
Set-SecretDefaultVault
orSet-SecretVaultDefault
.