Open horvatal opened 1 year ago
Hi @horvatal, thanks for opening the issue.
We are currently handling the casing issues by making the values read by the provider is consistent instead of ignoring the casing. Per the config file you provided, the target_capacity_reservation_group_id
was from azapi
provider, could you please provide the config block of that?
azapi
conbiane parent_id
and resource_name
to get the id of the target resource, I may wondering if the parent_id
specified was lower-cased.
For any further questions, please leave comments.
Is there an existing issue for this?
Community Note
Terraform Version
1.5.3
AzureRM Provider Version
3.65.0
Affected Resource(s)/Data Source(s)
azurerm_site_recovery_replicated_vm
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No change expected, if target_capacity_reservation_group_id only differs in letter casing (e.g. upper-case). Here this happens from Z-ACH-A9999-PR01-NS1-01-ASR to z-ach-a9999-pr01-ns1-01-asr. Azure documentation says that Resource Group names should be case-insensitive (https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#:~:text=Always%20perform%20a%20case%2Dinsensitive%20comparison%20of%20names).
Actual Behaviour
The target CRG was set by a Recovery Plan Runbook (with Get-AzCapacityReservationGroup in upper-case format). If I have a TF run a change is detected, because the azapi (Microsoft.Compute/capacityReservationGroups@2021-11-01) delivers lower-case RG in the ID.
Steps to Reproduce
No response
Important Factoids
No response
References
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#:~:text=Always%20perform%20a%20case%2Dinsensitive%20comparison%20of%20names