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
All of the necessary Terraform templates to recreate this issue are in this gist.
Expected Behavior
Terraform should have added/updated the tags on the Firewall.
Actual Behavior
Terraform added/updated the tags on the Firewall, and also deleted the network rule collection.
A subsequent terraform plan included the (re)creation of the network rule collection.
Steps to Reproduce
Using the Terraform templates in the linked gist, run terraform plan and terraform apply.
In the Azure portal, navigate to the firewall's network rule collections, and confirm the existence of the network rule collection described in the Terraform templates.
In the Terraform templates, make a change to the azurerm_firewall resource, e.g. add a new tag or edit an existing one in terraform.tfvars.
Run terraform plan and terraform apply again.
Refresh the network rule collections in the Azure portal.
Important Factoids
Our discovery of this issue came when updating tags to meet compliance, and the inadvertent removal of the above network rule collection led to some resources not having internet access briefly.
The text was updated successfully, but these errors were encountered:
I see the problem - the API treats the firewall as one big object so when the tags are updated it is overwriting the rules. I've submitted a PR to resolve
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Mar 5, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
Terraform Configuration Files
All of the necessary Terraform templates to recreate this issue are in this gist.
Expected Behavior
Terraform should have added/updated the tags on the Firewall.
Actual Behavior
Terraform added/updated the tags on the Firewall, and also deleted the network rule collection.
A subsequent
terraform plan
included the (re)creation of the network rule collection.Steps to Reproduce
terraform plan
andterraform apply
.azurerm_firewall
resource, e.g. add a new tag or edit an existing one interraform.tfvars
.terraform plan
andterraform apply
again.Important Factoids
Our discovery of this issue came when updating tags to meet compliance, and the inadvertent removal of the above network rule collection led to some resources not having internet access briefly.
The text was updated successfully, but these errors were encountered: