-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Firewall is recreated when Resource Group and/or the VNET-name contains uppercase letters #24983
Comments
Hi @Exchizz, thank you for bringing up this issue. Unfortunately, this is an intentional behavior of Terraform: it is case sensitive and AzureRM will standardize the API response to remove any differences in casing. In this situation, could you please use the correct casing for |
Hi @wuxu92, Unfortunately I cannot change This is only an problem in the |
@Exchizz, could you please provide the definition of |
This is the output from the
(I've updated the issue description. It is both the name of the VNET that contains uppercase letters and the name of the resource group. When I created the issue, I accidentally replace the resource group name with lowercase letters) |
@Exchizz xxrr Could you please help me if my understand is correct: the resource group name and vnet name were created in UPPER CASE, but the |
Exactly, yes 👍 |
I ran into this today, and unfortunately, I think it is an Azure API issue because if you look at the export template blade on the firewall resource within Azure you can see the VNET resource ID under |
Is there an existing issue for this?
Community Note
Terraform Version
v1.3.9
AzureRM Provider Version
3.92.0
Affected Resource(s)/Data Source(s)
azurerm_firewall
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
I would expect the firewall not to be recreated as the subnet_id is the same (except for the casing of the Resource Group and casing of the VNET name)
Actual Behaviour
The firewall is recreated
Steps to Reproduce
terraform plam/apply to create the firewall. Then running terraform plan/apply again causes this bug to happen.
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: