[Compute] sig image-version create: Support creating from a VHD#16371
[Compute] sig image-version create: Support creating from a VHD#16371
Conversation
|
Compute |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
| c.argument('target_region_encryption', nargs='+', | ||
| help='Space-separated list of customer managed keys for encrypting the OS and data disks in the gallery artifact for each region. Format for each region: `<os_des>,<lun1>,<lun1_des>,<lun2>,<lun2_des>`. Use "null" as a placeholder.') | ||
| c.argument('vhd', help='Source VHD URI of OS disk', min_api='2020-09-30') | ||
| c.argument('vhd_storage_account', help='Name or ID of storage account of source VHD URI of OS disk', min_api='2020-09-30') |
There was a problem hiding this comment.
could vhd resource in another tenant?
There was a problem hiding this comment.
Good question. If true, I need to add cross-tenant authentication.
|
I have a few questions looking at the api support. So a customer using VHD will supply vhd and vhd_storage_account flag, but not the os_snapshot flag?
|
|
hi @qwordy, what's status of this PR? is it ok to merge? |
|
|
@qwordy
|
|
@olayemio How about |
|
The OS part is done. |
|
@qwordy I propose the following |
|
Merge OS part first. Data disks will be in another PR. |
Description
Resolve #15868
[Compute] Upgrade gallery_image_versions to 2020-09-30
[Compute] sig image-version create: Support creating from a VHD
Testing Guide
History 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 feature.
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.
I adhere to the Error Handling Guidelines.