Open cailyoung opened 2 years ago
the current behavior is inconsistent with other places where Terraform does destroy/create where property cannot be updated in-place. It is also totally break the usage as it works fine for Premium SKU but just fails for Standard. It is not clear what do you expects users to do in this situation - manually destroy -target EventHub and then run apply ?
Also, the current behavior looks like a regression - before #13557 the current use case seems to have been working via destoy/recreate
Community Note
Terraform (and AzureRM Provider) Version
terraform 1.0.9 azurerm 2.98.0 (with beta3 resource opt-in)
Affected Resource(s)
azurerm_eventhub
Terraform Configuration Files
the var.azure_monitor_eventhub_partition_count was
4
in state, and we want to change it to32
. SKU isStandard
which supports 32 partitions.Debug Output
Panic Output
Expected Behaviour
Plan should indicate destroy/create is required as Standard SKU doesn't allow partition resize after creation.
Actual Behaviour
Plan indicated update-in-place, apply failed, with:
Steps to Reproduce
terraform apply
with partition count < 32.terraform apply
Important Factoids
References
13557 may have contributed here