-
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
Application Gateway with multiple request_routing_rule behaviour #13878
Comments
Hi @mne-unitn, thanks for this issue. Do you experience this on a functional level as well? To be honest, I think this might be a technical issue with the To fix the @tombuildsstuff Do you think we'd be able to fix this, or are we limited by the Terraform core? I'm not familiar enough with the "request_routing_rule": {
Type: pluginsdk.TypeSet,
Required: true,
MinItems: 1,
Elem: &pluginsdk.Resource{
Schema: map[string]*pluginsdk.Schema{
"name": {
Type: pluginsdk.TypeString,
Required: true,
},
"rule_type": {
Type: pluginsdk.TypeString,
Required: true,
ValidateFunc: validation.StringInSlice([]string{
string(network.ApplicationGatewayRequestRoutingRuleTypeBasic),
string(network.ApplicationGatewayRequestRoutingRuleTypePathBasedRouting),
}, false),
},
"http_listener_name": {
Type: pluginsdk.TypeString,
Required: true,
},
"backend_address_pool_name": {
Type: pluginsdk.TypeString,
Optional: true,
},
"backend_http_settings_name": {
Type: pluginsdk.TypeString,
Optional: true,
},
"url_path_map_name": {
Type: pluginsdk.TypeString,
Optional: true,
},
"redirect_configuration_name": {
Type: pluginsdk.TypeString,
Optional: true,
ValidateFunc: validation.StringIsNotEmpty,
},
"rewrite_rule_set_name": {
Type: pluginsdk.TypeString,
Optional: true,
ValidateFunc: validation.StringIsNotEmpty,
},
"backend_address_pool_id": {
Type: pluginsdk.TypeString,
Computed: true,
},
"backend_http_settings_id": {
Type: pluginsdk.TypeString,
Computed: true,
},
"http_listener_id": {
Type: pluginsdk.TypeString,
Computed: true,
},
"id": {
Type: pluginsdk.TypeString,
Computed: true,
},
"url_path_map_id": {
Type: pluginsdk.TypeString,
Computed: true,
},
"redirect_configuration_id": {
Type: pluginsdk.TypeString,
Computed: true,
},
"rewrite_rule_set_id": {
Type: pluginsdk.TypeString,
Computed: true,
},
},
},
}, |
I think you are right. Looking at the logs on the Azure side, it seems the api recognizes the correct diff and applies only the different configuration parts. thank you |
Hello @mne-unitn, @aristosvo please any update on this? I know there are related issues and some statements there promised this being fixed with coming 3.x release which apparently didn't happen. The problem still persists with even newest AzureRM provider and terraform core. It behaves as described here #16136
Also related - #6896 (comment) Thank you for any answer... |
Community Note
Terraform (and AzureRM Provider) Version
Terraform v1.0.8
provider registry.terraform.io/hashicorp/azurerm v2.82.0
Affected Resource(s)
azurerm_application_gateway
Terraform Configuration Files
Debug Output
Panic Output
Expected Behaviour
When I enable the second request_routing_rule (the one commented out), I would expect terraform to just add that specific rule.
Actual Behaviour
When I enable the second request_routing_rule (the one commented out), terraform destroys all the request_routing_rules and recreates them.
Steps to Reproduce
terraform apply
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: