search

Azure / bicep-registry-modules

Bicep registry modules
MIT License
466 stars 314 forks source link

[AVM Module Issue]: Unable to set value 'inboundIpAddressOverride' #3176

Open kevin-381ecc2e opened 1 week ago

kevin-381ecc2e commented 1 week ago

Check for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/web/hosting-environment

(Optional) Module Version

0.1.1

Description

When deploying an App Service Environment with Private VNET Integration you can provide an 'inboundIpAddressOverride' to pick a custom Ip within the subnet. However when deploying the module to Azure we receive the following error: 

Operation not supported: Cannot set or change Custom Inbound IP Address on Updates.

It seems that in the module first the appServiceEnvironment is being created on the following line https://github.com/Azure/bicep-registry-modules/blob/119f1cdf9437bfb392a53519f560884be395a021/avm/res/web/hosting-environment/main.bicep#L153

And afterwards the networkConfiguration gets deployed 'as an Update' on line https://github.com/Azure/bicep-registry-modules/blob/119f1cdf9437bfb392a53519f560884be395a021/avm/res/web/hosting-environment/main.bicep#L174

The Azure Portal mentions that it is not allowed to set the custom IP after the App Service Environment is deployed. I think it's necessary to include the network configuration in the 'appServiceEnvironment' resource to make this work.

(Optional) Correlation Id

No response

microsoft-github-policy-service[bot] commented 1 week ago

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

avm-team-linter[bot] commented 1 week ago

@kevin-381ecc2e, thanks for submitting this issue for the avm/res/web/hosting-environment module!

[!IMPORTANT] A member of the @Azure/avm-res-web-hostingenvironment-module-owners-bicep or @Azure/avm-res-web-hostingenvironment-module-contributors-bicep team will review it soon!

microsoft-github-policy-service[bot] commented 6 days ago

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
microsoft-github-policy-service[bot] commented 8 hours ago

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!
microsoft-github-policy-service[bot] commented 8 hours ago

[!CAUTION] This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-bicep) immediate attention as it hasn't been responded to within 6 business days.

[!TIP]

  • To avoid this rule being (re)triggered, the "Needs: Triage :mag:" and "Status: Response Overdue :triangular_flag_on_post:" labels must be removed when the issue is first responded to!
  • Remove the "Needs: Immediate Attention :bangbang:" label once the issue has been responded to.