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

azurerm_application_gateway configure backend_http_settings hostname #2258

Closed
test-in-prod opened this issue Nov 6, 2018 · 3 comments
Closed

Comments

@test-in-prod
Copy link

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

Description

Azure supports configuring backend HTTP setting rule to specify a Host Name (host header) when proxying requests. Right now terraform doesn't seem to have support for this in backend_http_settings.

New or Affected Resource(s)

  • azurerm_application_gateway

Potential Terraform Configuration

...

backend_http_settings {
    name                  = "${azurerm_virtual_network.vnet.name}-be-htst"
    cookie_based_affinity = "Disabled"
    port                  = 80
    protocol              = "Http"
    request_timeout       = 1
    host_name        = "backend-host.azurewebsites.net" # Host Name textbox
}

...

Now, I wonder if emulating the checkbox to pick from backend address, terraform could look into fqdn list of backend_address_pool respective via request_routing_rule.


Custom Host specified

2

Using backend address

1

@test-in-prod
Copy link
Author

test-in-prod commented Nov 6, 2018

I guess a temporary workaround could be running a null_resource provisioner that calls:

az network application-gateway http-settings update -g <rg name> --gateway-name <apg name> -n <http setting name> --host-name-from-backend-pool true

But this is not ideal since null_resource only runs when parent resource gets created.

@tombuildsstuff
Copy link
Contributor

hi @CryptonZylog

Thanks for opening this issue :)

Support for this has previously been requested in #1875 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of #1875 - please subscribe to that issue for updates.

Thanks!

@ghost
Copy link

ghost commented Mar 6, 2019

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!

@ghost ghost locked and limited conversation to collaborators Mar 6, 2019
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

2 participants