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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't update Azure CDN Origin Host Header #14968

Closed
phekmat opened this issue May 31, 2017 · 1 comment
Closed

Can't update Azure CDN Origin Host Header #14968

phekmat opened this issue May 31, 2017 · 1 comment

Comments

@phekmat
Copy link
Contributor

phekmat commented May 31, 2017

Terraform Version

0.9.6 (also tested with 0.9.4)

Affected Resource(s)

  • azurerm_cdn_endpoint

Terraform Configuration Files

resource "azurerm_cdn_profile" "cdn" {
  name                = "test-cdn"
  resource_group_name = "${azurerm_resource_group.test.name}"
  location            = "East US"
  sku                 = "Standard_Verizon"
}

resource "azurerm_cdn_endpoint" "cdn" {
  name                = "test-cdn"
  profile_name        = "${azurerm_cdn_profile.cdn.name}"
  resource_group_name = "${azurerm_resource_group.test.name}"
  location            = "East US"

  querystring_caching_behaviour = "UseQueryString"

  origin {
    name       = "${azurerm_storage_account.cdn.name}-blob-core-windows-net"
    host_name  = "${azurerm_storage_account.cdn.name}.blob.core.windows.net"
    http_port  = 80
    https_port = 443
  }

  origin_host_header = "${azurerm_storage_account.cdn.name}.blob.core.windows.net"
  origin_path = "/${azurerm_storage_container.cdn.name}/"
}

Expected Behavior

Changing the origin_host_header after the resource has been created should update the endpoint

Actual Behavior

The header remains unchanged and can be verified by rerunning terraform plan or looking at the endpoint in the portal.

Steps to Reproduce

  1. Add a CDN endpoint (with or without the origin_host_header)
  2. terraform apply
  3. Modify/add the origin_host_header
  4. terraform apply
@ghost
Copy link

ghost commented Apr 9, 2020

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants