Open peruzzof opened 11 months ago
@peruzzof thanks for opening this issue. I would like to confirm that you mean terraform should make private_ip_addresses property to be replaced when changing the address prefix of the subnet, correct? If yes, this is by design since private_ip_addresses
is a read-only property but not a user settable property.
Let me elaborate further.
This property is being used for the backend configuration of my Application Gateway and the "terraform plan" is not planning this change, but during apply phase the value changed and I get this error:
Error: Provider produced inconsistent final plan
When expanding the plan for azurerm_application_gateway.agw to include new
values learned so far during apply, provider
"registry.terraform.io/hashicorp/azurerm" produced an invalid new value for
.backend_address_pool: planned set element
cty.ObjectVal(map[string]cty.Value{"fqdns":cty.SetValEmpty(cty.String),
"id":cty.StringVal("/subscriptions/XXXXXXXXXXX/resourceGroups/XXXXXXX/providers/Microsoft.Network/applicationGateways/XXXXXXX/backendAddressPools/XXXXXX-appgateway-pool-test"),
"ip_addresses":cty.SetVal([]cty.Value{cty.StringVal("10.101.100.5")}),
"name":cty.StringVal("XXXXX-appgateway-pool-test")}) does not correlate
with any element in actual.
Is there an existing issue for this?
Community Note
Terraform Version
1.5.7
AzureRM Provider Version
3.72.0
Affected Resource(s)/Data Source(s)
azurerm_api_management
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
It will mark the apim internal ip as being replaced
Actual Behaviour
APIM is marking only the subnetid as to be replaced
Steps to Reproduce
Important Factoids
No response
References
No response