az feedback auto-generates most of the information requested below, as of CLI version 2.0.62
Related command
az keyvault backup start
az keyvault restore start
Describe the bug
I wasn't sure if this should be a bug or a feature. My request is to make the behavior between backup and restore more user friendly.
Currently when you call az keyvault backup start, it returns folderUrl that the backup will be stored in.
However, when you call az keyvault restore start, you can't just pass that URL to it in the --storage-resource-uri parameter, you have to separately pass the folder name in the --backup-folder parameter and strip the folder name from the URL if you are going to use --storage-resource-uri
Further, for az keyvault backup start, if you use --storage-resource-uri, you can't define the final path the backup is in. There are use cases where it would be nice to be able to control the folder name the backup ends up in instead of letting the HSM do it.
Related command
az keyvault backup start
az keyvault restore start
Describe the bug
I wasn't sure if this should be a bug or a feature. My request is to make the behavior between backup and restore more user friendly.
Currently when you call az keyvault backup start, it returns folderUrl that the backup will be stored in.
However, when you call az keyvault restore start, you can't just pass that URL to it in the --storage-resource-uri parameter, you have to separately pass the folder name in the --backup-folder parameter and strip the folder name from the URL if you are going to use --storage-resource-uri
Further, for az keyvault backup start, if you use --storage-resource-uri, you can't define the final path the backup is in. There are use cases where it would be nice to be able to control the folder name the backup ends up in instead of letting the HSM do it.