What's Changed
Documentation
- Clarify IPAM allocation rules and pool constraints in the module README (#105). Documents the Azure AVNM platform behavior verified against API
2025-09-01:- One IPv4 pool + one IPv6 pool per virtual network (and per subnet) — the RP rejects duplicate or multiple same-family pools (
CannotHaveDuplicatePoolIds,only one association of each IP type is allowed). - No mixing of IPAM pool allocation and static
address_prefixesin the same VNet/subnet (CannotMixAddressPrefixAndPoolInPayload). - Subnet pools must be a subset of the parent VNet's pools (
SubnetPoolsMustBeSubsetOfVnetPools). - Summarization vs. fragmentation of a single
number_of_ip_addressesallocation: Azure resolves one allocation entry into one or more CIDRs depending on contiguity of free space — this is read-only and causes no Terraform drift.
- One IPv4 pool + one IPv6 pool per virtual network (and per subnet) — the RP rejects duplicate or multiple same-family pools (
- New "IPAM Allocation Rules and Sizing" section plus expanded IPAM troubleshooting with RP error codes.
Docs-only patch release. No module behavior, inputs, or outputs changed. The validation introduced in v0.18.0 (one IPv4 + one IPv6 pool per VNet) was confirmed correct against the latest Azure API.
Contributors
- @haflidif — maintainer
- @jaredfholgate — review
Full Changelog: v0.18.0...v0.18.1