You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When upgrading our azurerm provider to version 3.37.0 we expected no changes when rerunning our provisioning.
Actual Behaviour
We got changes that force the replacement of three resources that depend on our azurerm_spring_cloud_service because the id attribute of that resource supposedly changed.
Strangely enough, the terraform plan shows no changes at all for the azurerm_spring_cloud_service resource itself and if we check the id of this resource (in the Azure portal) it still shows the "old" version of the id with *\Spring* instead of **\spring**.
Terraform plan output
azapi_resource.elastic["asc-cmn"] must be replaced
-/+ resource "azapi_resource" "elastic" {
~ id = "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/Spring/asc-cmn-dev/providers/microsoft.insights/diagnosticSettings/elastic" -> (known after apply)
...
~ parent_id = "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/Spring/asc-cmn-dev" -> "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/spring/asc-cmn-dev" # forces replacement
...
}
azurerm_monitor_diagnostic_setting.diag["asc-cmn"] must be replaced
-/+ resource "azurerm_monitor_diagnostic_setting" "diag" {
~ id = "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/Spring/asc-cmn-dev|monitoring" -> (known after apply)
~ target_resource_id = "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/Spring/asc-cmn-dev" -> "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/spring/asc-cmn-dev" # forces replacement
...
}
azurerm_role_assignment.<...>["asc-cmn"] must be replaced
-/+ resource "azurerm_role_assignment" "..." {
~ scope = "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/Spring/asc-cmn-dev" -> "/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/spring/asc-cmn-dev" # forces replacement
}
Only the dependent resources get changes and not the azurerm_spring_cloud_service. As far as we see the id of the service (in the azure portal) is: /subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/Spring/asc-cmn-dev
Steps to Reproduce
Set up an azurerm_spring_cloud_service and related azurerm_monitor_diagnostic_setting (or one of the two other dependent resources mentionned) using a version of the azurerm provider < 3.35.0.
Rerun terraform apply for the above project using provider version 3.37.0
Important Factoids
No response
References
We believe the issue we are experiencing might be related to: #19564
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Terraform Version
1.3.6
AzureRM Provider Version
3.37.0
Affected Resource(s)/Data Source(s)
azurerm_spring_cloud_service
Terraform Configuration Files
Debug Output/Panic Output
NA (we didn't execute the plan)
Expected Behaviour
When upgrading our azurerm provider to version 3.37.0 we expected no changes when rerunning our provisioning.
Actual Behaviour
We got changes that force the replacement of three resources that depend on our
azurerm_spring_cloud_service
because theid
attribute of that resource supposedly changed.Strangely enough, the terraform plan shows no changes at all for the
azurerm_spring_cloud_service
resource itself and if we check theid
of this resource (in the Azure portal) it still shows the "old" version of the id with *\Spring* instead of **\spring**.Terraform plan output
Only the dependent resources get changes and not the
azurerm_spring_cloud_service
. As far as we see the id of the service (in the azure portal) is:/subscriptions/.../resourceGroups/rg-asc-cmn-dev/providers/Microsoft.AppPlatform/Spring/asc-cmn-dev
Steps to Reproduce
azurerm_spring_cloud_service
and relatedazurerm_monitor_diagnostic_setting
(or one of the two other dependent resources mentionned) using a version of the azurerm provider < 3.35.0.terraform apply
for the above project using provider version 3.37.0Important Factoids
No response
References
We believe the issue we are experiencing might be related to:
#19564
The text was updated successfully, but these errors were encountered: