[KeyVault] az keyvault key list-versions: support parameter --id for specifying keys - #12129
Merged
Merged
Conversation
Bin Ma (bim-msft)
requested review from
Feng Zhou (fengzhou-msft) and
Jiashuo Li (jiasli)
as code owners
February 11, 2020 04:25
Contributor
|
Tested with version and without version. Both work fine: |
Jiashuo Li (jiasli)
approved these changes
Feb 11, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make the behavior consistent with other operations of key.
For operations:
backup/delete/download/list-versions/purge/recover/set-attributes/show/show-deleted, we should support the following both command types:az keyvault key {operation} -n {key_name} --vault-name {kv}az keyvault key {operation} --id {key_id}Also for
az keyvault secretandaz keyvault certificate.This 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.