Azure / Azure/bicep-registry-modules
[AVM Module Issue]: Virtual Network with subnets created using AVM bicep module is failing to be associated with Azure Virtual Network Manager (AVNM) IP Address pool (IPAM)
- 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?
I'm not sure
### Module Name
avm/res/network/virtual-network
### (Optional) Module Version
_No response_
### Description
If you create VNet **with subnets** using `br/public:avm/res/network/virtual-network:0.7.0` module and then try to associate VNet with Azure Virtual Network Manager IP Address Pool (IPAM), it will fail with the following error message.
```
Error: Invalid configuration on subnet ......; cannot populate both address prefix and address prefixes.
```
It looks like that both `addressPrefix` and `addressPrefixes` subnet properties are set during deployment.
It might be that this is a bug at AVNM side, but I report it here anyways :)
### (Optional) Correlation Id
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.