Skip to content

Conversation

@bim-msft
Copy link
Contributor

@bim-msft bim-msft commented Feb 11, 2020

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:

  1. az keyvault key {operation} -n {key_name} --vault-name {kv}
  2. az keyvault key {operation} --id {key_id}

Also for az keyvault secret and az keyvault certificate.


This checklist is used to make sure that common guidelines for a pull request are followed.

@bim-msft bim-msft self-assigned this Feb 11, 2020
@bim-msft bim-msft added this to the S165 milestone Feb 11, 2020
@jiasli
Copy link
Member

jiasli commented Feb 11, 2020

Tested with version and without version. Both work fine:

az keyvault key list-versions --id https://{}.vault.azure.net/keys/key1/16a74f9d3993457b8cf9693103af8902
az keyvault key list-versions --id https://{}.vault.azure.net/keys/key1

@bim-msft bim-msft merged commit d08a739 into Azure:dev Feb 11, 2020
@bim-msft bim-msft deleted the bim_kv_fix_listversions branch February 11, 2020 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants