Changing ultra_ssd_enabled should not force recreation

[NilsBusche]

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 "+1" or "me too" comments, 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

Terraform (and AzureRM Provider) Version

• Terraform v0.12.24
• terraform-provider-azurerm_v2.16.0_x5

Affected Resource(s)

• azurerm_linux_virtual_machine
• azurerm_windows_virtual_machine

Terraform Configuration Files

resource "azurerm_linux_virtual_machine" "instance" {

  [...]

  additional_capabilities {
    ultra_ssd_enabled = false
  }
}

Expected Behavior

Changing ultra_ssd_enabled should be possible without recreation if the VM is stopped/deallocated.

Actual Behavior

Changing ultra_ssd_enabled requires recreation of the VM resource also if the VM is stopped/deallocated. This possible using Azure CLI as well.

Steps to Reproduce

1. Create configuration for a virtual machine as described above
2. terraform apply
3. Change ultra_ssd_enabled to true
4. terraform plan/apply

[jpbuecken]

This logic is similar to SKU (instance size) change, isn't it? -> Offline possible, no recreate needed.

[ghost]

This has been released in version 2.25.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.25.0"
}
# ... other configuration ...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!