azurerm_machine_learning_compute_cluster virtual_machine_size is inconsistent due to case

[mattmshell]

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 "+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 Version

1.1.8

AzureRM Provider Version

3.8.0

Affected Resource(s)/Data Source(s)

azurerm_machine_learning_compute_cluster

Terraform Configuration Files

resource "azurerm_machine_learning_compute_cluster" "cluster" {
  for_each = var.compute_clusters

  name                          = "foo"
  location                      = var.location
  machine_learning_workspace_id = azurerm_machine_learning_workspace.aml_ws.id
  virtual_machine_size          = each.value.vm_size
  subnet_resource_id            = each.value.subnet_id
}

Debug Output/Panic Output

-/+ resource "azurerm_machine_learning_compute_cluster" "foo" {
 	...
	~ vm_size                       = "STANDARD_DS2_V2" -> "Standard_DS2_V2" # forces replacement
	...
}

Expected Behaviour

azurerm_machine_learning_compute_cluster is not replaced

Actual Behaviour

azurerm_machine_learning_compute_cluster is replaced

Steps to Reproduce

terraform apply

Important Factoids

for_each expression

References

No response

[mattmshell]

Both azurerm_machine_learning_compute_cluster.virtual_machine_size and azurerm_machine_learning_compute_instance.vm_size appear to suffer from this problem.

Originally azurerm_machine_learning_compute_instance triggered this issue. After upgrading to Terraform v1.2.7 and AzureRM v3.18.0, azurerm_machine_learning_compute_cluster caused the same problem.

Uppercase input appears to resolve the problem, but I generally don't think the vm_size should be case sensitive.

[ms-henglu]

Hi @mattmshell ,

Thank you for taking time to report this issue!

I believe this is a server-side bug that it returns vmSize in upper case.

[ms-henglu]

I've created an issue in swagger repo to track it:Azure/azure-rest-api-specs#20336