Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frontdoor persistent diff #25911

Open
1 task done
VenelinMartinov opened this issue May 8, 2024 · 0 comments
Open
1 task done

Frontdoor persistent diff #25911

VenelinMartinov opened this issue May 8, 2024 · 0 comments

Comments

@VenelinMartinov
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

1.8.2

AzureRM Provider Version

3.102.0

Affected Resource(s)/Data Source(s)

azurerm_frontdoor

Terraform Configuration Files

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"
  }
}

Debug Output/Panic Output

https://gist.github.com/VenelinMartinov/e93307a9682d266b5a5e5e6c6f630355

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?

Steps to Reproduce

  1. terraform apply
  2. terraform plan

Important Factoids

No response

References

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant