Subnet create/update support for IPAM pool association

[p-thompson]

Related command

az network vnet subnet create
az network vnet subnet update

Is your feature request related to a problem? Please describe.

Feature request for the subnet create/update commands to introduce a new parameter: --ipam-pool-prefix-allocations. This enhancement aims to facilitate the association/disassociation of a subnet with an IP Address Management (IPAM) pool, thereby streamlining the allocation of address prefixes.

This feature support is crucial for IPAM service going GA, which was targeted for late-May.

https://learn.microsoft.com/en-us/cli/azure/network/vnet/subnet?view=azure-cli-latest#az-network-vnet-subnet-create
https://learn.microsoft.com/en-us/cli/azure/network/vnet/subnet?view=azure-cli-latest#az-network-vnet-subnet-update

Describe the solution you'd like

New Parameter details:

• Optional Parameter
• Enables customers to specify an IPAM pool for allocating address prefixes to resources within the subnet, instead of defining an address prefix during - subnet creation/update.
• If this parameter is utilized, the addressPrefixes array must explicitly be empty. Otherwise, a default address prefix will be used, causing an error.

Describe alternatives you've considered

We have tried the workaround of creating a subnet with address prefixes and then removing them to instead set an ipamPoolPrefixAllocation, however this does not work; example below:
az network vnet update -g ipam-test-rg -n testVnet5825 --address-prefixes "" --set 'subnets[0].ipamPoolPrefixAllocations=[{"numberOfIpAddresses":"256","pool":{"id":"/subscriptions/c9295b92-3574-4021-95a1-26c8f74f8359/resourceGroups/ipam-test-rg/providers/Microsoft.Network/networkManagers/ipam-test-nm/ipamPools/paigetest1025"}}]'

argument --address-prefixes: expected at least one argument

Additional context

The requested new parameter already exists for vnet create and vnet update; we just need it for subnet as well

[yonzhan]

Thank you for opening this issue, we will look into it.

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• Bug fix request: VNET update command is incorrectly overwriting a property. #31294

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

For command, az network vnet update the parameters --address-prefixes and --ipam-pool-prefix-allocations are mutually exclusive; only one can be provided at a time.

Expectation/Feature Request:

• Allow empty array for param --ipam-pool-prefix-allocations. Empty array is valid input.
• If both are provided, and the pool param is a non-empty array, then use ipam pool as is and set address prefixes to an empty array.
• If both are provided, and the ipam pool is an empty array, use the address prefix and pool as is.

Reference:

• Bug fix request: VNET update command is incorrectly overwriting a property. #31294 (comment)

Powered by issue-sentinel