[FEATURE REQ] Add InboundIpAddress data to WebSiteData

[wbarisch]

Library name

Azure.ResourceManager.AppService v1.3.0

Please describe the feature.

Currently public partial class WebSiteData : TrackedResourceData has some of the properties from a WebApp Resource JSON, but not all.
I would like to request that the InboundIpAddress data would be added to the WebSiteData class.

This helps developers to use the inbound ip address to set new custom domains using azure-sdk-for-net.

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[mcgallan]

@wbarisch Thank you for reaching out to us. I will forward your request to the Swagger team for further consideration. In the meantime, if you require this attribute to proceed with your project, you can use the following code as a temporary workaround to obtain the InboundIpAddress:

var outboundIpAddress = websiteResource.Data.OutboundIPAddresses;
string[] ipArray = outboundIpAddress.Split(',');
var inboundIpAddress = ipArray[ipArray.Length - 1];

Additionally, if your goal is to bind a custom domain to your WebSite, you can achieve this using the HostNameBinding resource available in the azure-sdk-for-net. This will allow you to configure the domain binding seamlessly.

[github-actions]

Hi @wbarisch. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[wbarisch]

@mcgallan thank you for the workaround!
Can I rely on always using the last entry of the OutboundIPAddresses as an inbound Ip Address?

[mcgallan]

@mcgallan thank you for the workaround! Can I rely on always using the last entry of the OutboundIPAddresses as an inbound Ip Address?

Yes, you can use this method to get the inbound IP address, but if you are not required to use only the SDK, I would recommend checking it directly on the Azure portal. Although the InboundIPAddress is not exposed in the SDK currently, you can directly view it on your website's page.

[github-actions]

Hi @wbarisch. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[github-actions]

Hi @wbarisch, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[wbarisch]

@mcgallan Thank you, I will use the last IP from outboundIpAddresses for now. Let me know if you implement this feature in the future.
Best regards,
Wesley

[mcgallan]

@mcgallan Thank you, I will use the last IP from outboundIpAddresses for now. Let me know if you implement this feature in the future. Best regards, Wesley

@wbarisch Thank you for your feedback. We will certainly escalate this issue to our service team for review. However, I’d like to inform you that the process of receiving feedback from the service team, incorporating the requested feature into a new API version, and then generating a stable SDK version for customer use can be quite time-consuming. Given the busy schedule of the AppService team, they may not always be able to respond to requests immediately. It’s also important to note that the implementation of new feature requests falls outside the scope of the SDK team's responsibilities.

To help expedite this process, I would recommend submitting the feature request directly through open an Azure support request. This will help move things forward more efficiently. If we are able to successfully add this parameter to the SDK in a future release, we will make sure to highlight it in the release changelog.

For now, I will proceed with closing this issue. Should you have any further questions, please don’t hesitate to reach out.

[github-actions]

Hi @wbarisch. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

[github-actions]

Hi @wbarisch, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.