Open J0F3 opened 4 hours ago
Workaround is to set:
lifecycle {
ignore_changes = [infrastructure_resource_group_name]
}
Interestingly this "fixes" also all the other in-place updates shown above so that terraform plan
shows 'no changes' after the initial apply as expected.
Is there an existing issue for this?
Community Note
Terraform Version
1.9.5
AzureRM Provider Version
4.2.0
Affected Resource(s)/Data Source(s)
azurerm_container_app_environment
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Terraform apply should show no changes after initial apply. (Or at least it should update the
infrastructure_resource_group_name
in place as it is the case of other properties like static_ip_address, default_domain, etc.)Actual Behaviour
On every apply the Azure Container App Environment get recreated because of unexpected change of
infrastructure_resource_group_name
.Steps to Reproduce
terraform apply ( a second time)
Important Factoids
No response
References
While a custom resouce group can be specified it should also work with the default name (without specify any name) as it is the recommend way by Microsoft:
Otherwise, the provider should give an error when
infrastructure_resource_group_name
is specified butinfrastructure_resource_group_name
not.