-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Support Auto OS Upgrade and Update Policy arguments in Az VMSS Update #29355
Labels
Auto-Assign
Auto assign by bot
Azure CLI Team
The command of the issue is owned by Azure CLI team
Compute
az vm/vmss/image/disk/snapshot
feature-request
Milestone
Comments
Thank you for opening this issue, we will look into it. |
Hi @maulikshah23, can I ask if this feature is related to security? |
Hi @maulikshah23, currently we may not have more effort to develop this feature. May I ask if it would be acceptable to have the next sprint (09-03) as the ETA? |
okay, we will release this feature in this sprint (08-06) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Auto-Assign
Auto assign by bot
Azure CLI Team
The command of the issue is owned by Azure CLI team
Compute
az vm/vmss/image/disk/snapshot
feature-request
Preconditions
Related command
az vmss create --name myScaleSet --resource-group myResourceGroup --enable-auto-os-upgrade true --upgrade-policy-mode Rolling
the above command is supported during provisioning, however the below command needs to be supported for customers enabling auto upgrade post provisioning
az vmss update --name myScaleSet --resource-group myResourceGroup --enable-auto-os-upgrade true --upgrade-policy-mode Rolling
Resource Provider
Compute Resource Provider
Description of Feature or Work Requested
The az vmss update command does not allow customers to enable Auto OS Image Upgrade with rolling upgrade policy from CLI. Customers have to use powershell or other mechanisms to complete this action.
To improve customer experience, both the az vmss create and az vmss update commands need to be supported.
Minimum API Version Required
Use Compute API version 2018-10-01 or higher
Swagger PR link / SDK link
N/A
Request Example
PUT or PATCH on
/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/Microsoft.Compute/virtualMachineScaleSets/myScaleSet?api-version=2021-03-01
Target Date
2024-07-30
PM Contact
Maulik Shah
Engineer Contact
Mike Richmond
Additional context
No response
The text was updated successfully, but these errors were encountered: