Support for inbound_ip_address and possible_inbound_ip_addresses for web_apps #24372
Open
1 task done
Labels
enhancement
service/app-service
upstream/microsoft
Indicates that there's an upstream issue blocking this issue/PR
v/3.x
Is there an existing issue for this?
Community Note
Description
This seems to have popped up in the past with #5333, #14385 and #14642 but they are for the older azurerm_app_service so seem to have slipped through the cracks. This is for v3.x of the azurerm provider.
I have an azurerm_windows_web_app with a custom hostname binding to an apex domain and thus I need to create a DNS A Record as you cannot use CNAME records for apex domains.
The Azure REST api exposes "inboundIpAddress" and "possibleInboundIpAddresses" as properties adjacent to the "outboundIpAddresses" and "possibleOutboundIpAddresses" that have already been surfaced by the azurerm_windows_web_app and azurerm_linux_web_app resources so it should be fairly trivial to mirror these properties for their inbound equivalent.
I'll happily have a go at implementing and create a pull request as I think it should just be a matter of following the pattern for the outbound properties.
New or Affected Resource(s)/Data Source(s)
Potential Terraform Configuration
No response
References
#5333
#14385
#14642
The text was updated successfully, but these errors were encountered: