Azure / Azure/bicep-registry-modules
[AVM Module Issue]: Add support for creating Virtual WAN Hub Connections
- Dominant language
- Bicep
- Stars
- 736
- Forks
- 564
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 30
Description
### Check for previous/existing GitHub issues
- [X] I have checked for previous/existing GitHub issues
### Issue Type?
Feature Request
### Module Name
avm/res/network/virtual-network
### (Optional) Module Version
_No response_
### Description
The virtual-network module currently supports peering to regular Azure VNets:
```
peerings: [
{
allowForwardedTraffic: true
allowGatewayTransit: false
allowVirtualNetworkAccess: true
remotePeeringAllowForwardedTraffic: true
remotePeeringAllowVirtualNetworkAccess: true
remotePeeringEnabled: true
remotePeeringName: 'customName'
remoteVirtualNetworkResourceId: ''
useRemoteGateways: false
}
```
It would be great to also support Azure Virtual WAN Hub connections.
As a reference, the Azure Landing Zones vending machine module has implemented support for this - see [here](https://github.com/Azure/bicep-registry-modules/blob/main/avm/ptn/lz/sub-vending/modules/subResourceWrapper.bicep#L397-L421).
### (Optional) Correlation Id
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.