You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using the recent http_listener host_names feature in the 2.8 azurerm provider: PR
It works, but in the end the behavior in the Azure portal is like this:
the App Gw Listeners entries no longer have a value on the Host name column.
clicking on such a Listener entry will display a warning that This Basic HTTP listener cannot use the same frontend port as an existing listener.
and in the bottom side of that edit pane for the Listener, the option for Listener type is switched to Basic, as opposed before the update when it was set to Multi site
the value for Host name is also missing, since it is only available under Multi site
My concern is that it might at some point send the wrong Host: header to one of the backends. Since I have more that one.
And also that I will be unable to make quick changes from the web portal if needed, since the current error/warning will prevent me from saving that edit pane.
The text was updated successfully, but these errors were encountered:
After tested, seems host_name in tfconfig maps to "host name" column in azure portal but host_names doesn't map to this column. So it doesn't show in this column.
Seems "http listener" is associated with "host names" according by below response from rest api. So I assume your concern should have been handled by API.
So would you ok to close this issue for now? Feel free to reopen it if you run into it again. Thank you.
Hi, (sorry for the late response) Yes, you are right, the template for that resource has the proper definition in the end. Only the web portal shows that error. And, sadly, for that reason I had to revert to host_name instead of host_names.
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
locked and limited conversation to collaborators
Jun 27, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was using the recent http_listener host_names feature in the 2.8 azurerm provider: PR
It works, but in the end the behavior in the Azure portal is like this:
Host name
column.This Basic HTTP listener cannot use the same frontend port as an existing listener.
Host name
is also missing, since it is only available under Multi siteThe App Gw module I'm using is very similar with the one from here: dfar-io/terraform-azurerm-app-gateway
with a
and
resource definitions inside
azurerm_application_gateway
And these variables in the module call:
My concern is that it might at some point send the wrong Host: header to one of the backends. Since I have more that one.
And also that I will be unable to make quick changes from the web portal if needed, since the current error/warning will prevent me from saving that edit pane.
The text was updated successfully, but these errors were encountered: