We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Get a secret that doesn't exist.
PS C:\Scripts> Get-Secret -Name 'blalba' or PS C:\Scripts> Get-Secret -Name 'blalba' -Vault "impactAutomation"
PS C:\Scripts> Get-Secret -Name 'blalba'
PS C:\Scripts> Get-Secret -Name 'blalba' -Vault "impactAutomation"
Verbose should not report success if the secret doesn't exist.
VERBOSE: Secret information was successfully retrieved from vault ImpactAutomation.
VERBOSE: Secret information was successfully retrieved from vault ImpactAutomation. Get-Secret : The secret blalba was not found. At line:1 char:1 + Get-Secret -Name 'blalba' + ~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Microsoft.Power...etSecretCommand:GetSecretCommand) [Get-Secret], ItemNotFoundException + FullyQualifiedErrorId : GetSecretNotFound,Microsoft.PowerShell.SecretManagement.GetSecretCommand
Name Value ---- ----- PSVersion 5.1.19041.1320 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.19041.1320 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
None
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Prerequisites
Steps to reproduce
Get a secret that doesn't exist.
PS C:\Scripts> Get-Secret -Name 'blalba'
or
PS C:\Scripts> Get-Secret -Name 'blalba' -Vault "impactAutomation"
Expected behavior
Verbose should not report success if the secret doesn't exist.
Actual behavior
VERBOSE: Secret information was successfully retrieved from vault ImpactAutomation.
Error details
Environment data
Version
None
Visuals
No response
The text was updated successfully, but these errors were encountered: