Skip to content
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 for rolling_upgrade_policy in azurerm_orchestrated_virtual_machine_scale_set #28270

Open
1 task done
darren-johnson opened this issue Dec 13, 2024 · 1 comment · May be fixed by #28354
Open
1 task done

Support for rolling_upgrade_policy in azurerm_orchestrated_virtual_machine_scale_set #28270

darren-johnson opened this issue Dec 13, 2024 · 1 comment · May be fixed by #28354

Comments

@darren-johnson
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

When using the newer azurerm_orchestrated_virtual_machine_scale_set resource instead of azurerm_windows_virtual_machine_scale_set there is no option to configure the rolling upgrade policy can this please be added.

New or Affected Resource(s)/Data Source(s)

azurerm_orchestrated_virtual_machine_scale_set

Potential Terraform Configuration

resource "azurerm_orchestrated_virtual_machine_scale_set" "this" {

... # Rest Of Configuration

  rolling_upgrade_policy {
      cross_zone_upgrades_enabled             = false
      max_batch_instance_percent              = 50
      max_unhealthy_instance_percent          = 50
      max_unhealthy_upgraded_instance_percent = 50
      pause_time_between_batches              = "PT30S"
      prioritize_unhealthy_instances_enabled  = true
      maximum_surge_instances_enabled         = true    
  }

}

References

No response

@rcskosir
Copy link
Contributor

rcskosir commented Jan 7, 2025

Thank you for taking the time to open this issue. Please subscribe to PR #28354 created for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants