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

Support for inbound_ip_address and possible_inbound_ip_addresses for web_apps #24372

Open
1 task done
EamonHetherton opened this issue Jan 3, 2024 · 1 comment
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

Comments

@EamonHetherton
Copy link

EamonHetherton commented Jan 3, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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 and review the contribution guide to help.

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)

  • azurerm_windows_web_app
  • azurerm_linux_web_app

Potential Terraform Configuration

No response

References

#5333
#14385
#14642

@xiaxyi
Copy link
Contributor

xiaxyi commented Jan 15, 2024

Hi @EamonHetherton, Thanks for raising this issue, terraform support for this property is blocked until it's exposed by azure rest api. I've raised the issue in api repo and we can track it via Azure/azure-rest-api-specs#27377.

Before the feature is supported, you can use the workaround to use resourece azurerm_dns_a_record that mentioned in the issue #14385

@mybayern1974 mybayern1974 added the upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR label Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement service/app-service upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR v/3.x
Projects
None yet
4 participants