We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.8.2
3.102.0
azurerm_frontdoor
terraform { required_providers { azurerm = { source = "hashicorp/azurerm" version = "3.102.0" } } } # Configure the Microsoft Azure Provider provider "azurerm" { features {} } resource "azurerm_resource_group" "example" { name = "resourceGroup" location = "West Europe" } resource "azurerm_frontdoor" "example" { name = "example476" resource_group_name = azurerm_resource_group.example.name routing_rule { name = "rule1" accepted_protocols = ["Http", "Https"] patterns_to_match = ["/*"] frontend_endpoints = ["frontEndEndpoint1"] forwarding_configuration { forwarding_protocol = "MatchRequest" backend_pool_name = "exampleBackendBing" } } backend_pool_load_balancing { name = "exampleLoadBalancingSettings1" } backend_pool_health_probe { name = "exampleHealthProbeSetting1" protocol = "Https" probe_method = "HEAD" } backend_pool { name = "exampleBackendBing" backend { host_header = "www.bing.com" address = "www.bing.com" http_port = 80 https_port = 443 } load_balancing_name = "exampleLoadBalancingSettings1" health_probe_name = "exampleHealthProbeSetting1" } frontend_endpoint { name = "frontEndEndpoint1" host_name = "example476.azurefd.net" } }
https://gist.github.com/VenelinMartinov/e93307a9682d266b5a5e5e6c6f630355
Upon running plan after apply, I expect there to be no diff in the resource.
A diff is produced on backend_pool_settings and cache_query_parameters every time.
Should the property be Computed given that the provider is setting it?
terraform-provider-azurerm/internal/services/frontdoor/frontdoor_resource.go
Line 2072 in 0e9b08f
terraform apply
terraform plan
No response
The text was updated successfully, but these errors were encountered:
Patch frontdoor permadiff (#2014)
c70fbe2
fixes #1421 by patching the upstream resource to be computed as the provider sets a value for it. This is needed for pulumi/pulumi-terraform-bridge#1936 works around hashicorp/terraform-provider-azurerm#25911 issue for patch: #2015 upstream PR: hashicorp/terraform-provider-azurerm#25912
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Community Note
Terraform Version
1.8.2
AzureRM Provider Version
3.102.0
Affected Resource(s)/Data Source(s)
azurerm_frontdoor
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Upon running plan after apply, I expect there to be no diff in the resource.
Actual Behaviour
A diff is produced on backend_pool_settings and cache_query_parameters every time.
Should the property be Computed given that the provider is setting it?
terraform-provider-azurerm/internal/services/frontdoor/frontdoor_resource.go
Line 2072 in 0e9b08f
Steps to Reproduce
terraform apply
terraform plan
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: