Skip to content

Mitigate Get-AzKeyVaultSecret: Invalid Parameter AsPlainText #16730

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

Merged
merged 1 commit into from
Jan 4, 2022
Merged

Mitigate Get-AzKeyVaultSecret: Invalid Parameter AsPlainText #16730

merged 1 commit into from
Jan 4, 2022

Conversation

rmuralidhar
Copy link
Contributor

@rmuralidhar rmuralidhar commented Dec 29, 2021

When I copied the code and executed it, I received the below error,

Get-AzKeyVaultSecret: A parameter cannot be found that matches parameter name 'AsPlainText'.

I have tested this fix with one of my Key Vaults. I was able to verify the file generated as result is valid and usable.

Description

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
      • {Please put the link here}
    • the markdown help files have been regenerated using the commands listed here

When I copied the code and executed it, I received the below error, 

Get-AzKeyVaultSecret: A parameter cannot be found that matches parameter name 'AsPlainText'.

I have tested this fix with one of my Key Vaults. I was able to verify the file generated as result is valid and usable.
@ghost ghost added the customer-reported label Dec 29, 2021
@ghost
Copy link

ghost commented Dec 29, 2021

Thank you for your contribution rmuralidhar! We will review the pull request and get back to you soon.

@wyunchi-ms
Copy link
Contributor

/azp run azure-powershell - security-tools

@azure-pipelines
Copy link
Contributor

Azure Pipelines successfully started running 1 pipeline(s).

@wyunchi-ms wyunchi-ms merged commit 497e1fa into Azure:main Jan 4, 2022
@rmuralidhar rmuralidhar deleted the patch-1 branch January 4, 2022 13:36
@rmuralidhar
Copy link
Contributor Author

rmuralidhar commented Jan 11, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants