Closed LukeCarrier closed 3 years ago
Any idea when this will be available?
Bump.
This is required to be able to automatically bind DNS to an Azure Function App.
There even seems to be a forked commit fixing the issue - https://github.com/LukeCarrier/terraform-provider-azurerm/commit/2642118c55618ac3491179049af38f7f8f07916b
If you're using a custom hostname binding, that ip address can be accessed with the following reference.
Since this issue seems to have been addressed in the latest versions of the provider (or a valid workaround was provided) - I'm going to close it. Please open a new updated bug report if this is still relevant. Thank you.
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.
Community Note
Description
At the moment Terraform gives us the outbound IP addresses for the app in the following fields:
outbound_ip_addresses
possible_outbound_ip_addresses
I propose adding the same properties for the inbound direction:
inbound_ip_address
possible_inbound_ip_addresses
These are necessary for users trying to configure DNS records at the apex of a domain, where CNAMEs to the
default_hostname
aren't possible.The ARM API definitely gives us access to these properties -- e.g.
GET /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/my-rg/providers/Microsoft.Web/sites/my-site
:New or Affected Resource(s)
azurerm_function_app
azurerm_app_service
Potential Terraform Configuration
References
None