-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Keyvault] az keyvault key get-attestation: Support getting a MHSM key's attestation
#31427
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
Conversation
️✔️AzureCLI-FullTest
|
|
Hi @evelyn-ys, |
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| keyvault key get-attestation | cmd keyvault key get-attestation added |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
Related command
az keyvault key get-attestationDescription
New feature in keyvault key
7.6-preview.2Add new command
az keyvault key get-attestationto support getting a Managed HSM key's attestationTesting Guide
To get a key's attestation:
az keyvault key get-attestation --hsm-name $hsmName --name $keyNameTo store the attestation in a file:
az keyvault key get-attestation --hsm-name $hsmName --name $keyName --file attestation.jsonHistory Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.