-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_application_gateway: reordering blocks leads to change on every apply. #6452
Comments
My guess is that these should be schema.TypeSet instead of schema.TypeList in the schema, since the Azure API apparently doesn't care what the order is, and just ignores your change if you've only changed the order. |
The same issue actually occurs with all the other blocks, like redirect_configuration or request_routing_rule, etc, etc. Not only frontend_port. |
Hi @bailsman thanks for the issue. |
…rdering-issue Update `azurerm_application_gateway` - fix #6452 change `frontend_port`, `redirect_configuration` and `request_routing_rule` to TypeSet
This has been released in version 2.7.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.7.0"
}
# ... other configuration ... |
the problem is also present in http_listener, redirect_configuration and request_routing_rule.
|
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 👉 [email protected]. Thanks! |
Community Note
Terraform (and AzureRM Provider) Version
v0.12.24
v2.5.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Take a look at the frontend_port named "my_order_matters".
If you apply this configuration, then swap the order of the two frontend ports (so that "my_order_matters" is above the other frontend_port instead of below) - I'm expecting this to make no difference whatsoever.
terraform apply would say "Apply complete! Resources: 0 added, 0 changed, 0 destroyed."
Actual Behavior
After applying the configuration and swapping the order of the two blocks, terraform has the following plan:
Applying this change has no effect. After applying, it still wants to do the same change, no matter how many times you apply.
Steps to Reproduce
terraform apply
terraform apply
terraform apply
againImportant Factoids
The same issue actually occurs with the other blocks, like redirect_configuration or request_routing_rule. frontend_port is just an example.
References
The text was updated successfully, but these errors were encountered: