Support for setting rolling_upgrade_policy on azurerm_linux_virtual_machine_scale_set when using Manual upgrade_mode

[mouellet]

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

A rolling_upgrade_policy block cannot be specified when upgrade_mode is set to Manual using the provider but it is possible using the cli.

One might want to trigger a rolling upgrade manually (using the az vmss rolling-upgrade start command) but still benefit from the policy, i.e. using batch, pauses, etc.

You could always add the attribute to the lifecycle.ignore_changes list and set it using the cli, but that cannot be configured dynamically...

Also, why does both rolling_upgrade_policy and upgrade_mode attribute forces a new resource to be created on changes?

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

azurerm_linux_virtual_machine_scale_set

Potential Terraform Configuration

No response

References

No response