-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Compute] vm/vmss update: Add --priority; vm/vmss update: Add --max-price #11494
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
…Spot' to 'Priority' enum property; [Breaking change] Rename '--max-billing' parameter to '--max-price', for both VM and VMSS, to be consistent with Swagger and Powershell cmdlets
| "To enable Multitenant Hosting Rights for Windows 10, use 'Windows_Client'. " \ | ||
| "For more information see the Azure Windows VM online docs." | ||
| c.argument('license_type', help=license_msg, arg_type=get_enum_type(['Windows_Server', 'Windows_Client', 'None'])) | ||
| c.argument('priority', resource_type=ResourceType.MGMT_COMPUTE, min_api='2019-03-01', |
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.
curious about the min_api. If the min_api is different in vm and vmss, should we keep them separated?
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.
Yes, we should. This the cause of error in Profile 2019-03-01, which uses 2017-12-01 for compute.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Issue #11187
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).
I adhere to the Command Guidelines.