Azure / bicep-registry-modules

Bicep registry modules
MIT License
523 stars 370 forks source link

[AVM Module Issue]: `avm/ptn/network/hub-networking` Hub Firewall IP output #3875

Open ilhaan opened 16 hours ago

ilhaan commented 16 hours ago

Check for previous/existing GitHub issues

Issue Type?

I'm not sure

Module Name

avm/ptn/network/hub-networking

(Optional) Module Version

No response

Description

Is there a reason why the firewall private IP address is not included as an output in the avm/ptn/network/hub-networking module? When building out a hub and spoke network as described here, we would need to route traffic from each spoke to the hub firewall. That means in each spoke definition using this module, we would need to reference the Firewall's private IP address in the route table.

Am I missing something here? Are users expected to obtain the firewall IP some other way?

(Optional) Correlation Id

No response

avm-team-linter[bot] commented 16 hours ago

@ilhaan, thanks for submitting this issue for the avm/ptn/network/hub-networking module!

[!IMPORTANT] A member of the @Azure/avm-ptn-network-hubnetworking-module-owners-bicep or @Azure/avm-ptn-network-hubnetworking-module-contributors-bicep team will review it soon!

microsoft-github-policy-service[bot] commented 16 hours 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.