-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Compute] sig image-version create: Support creating from a VHD #16371
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
|
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could vhd resource in another tenant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.