Enable the association of additional IPv4 CIDR blocks with a VPC using IPAM by exposing the native resource arguments ipv4_ipam_pool_id and ipv4_netmask_length.
Motivation and Context
This update addresses a limitation where the association of additional IPv4 CIDR blocks with a VPC was previously restricted to static CIDR configurations. We can now configure a VPC to dynamically associate secondary CIDR blocks allocated from IPAM.
How Has This Been Tested?
[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects
[x] I have executed pre-commit run -a on my pull request
This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days
Description
Enable the association of additional IPv4 CIDR blocks with a VPC using IPAM by exposing the native resource arguments
ipv4_ipam_pool_id
andipv4_netmask_length
.Motivation and Context
This update addresses a limitation where the association of additional IPv4 CIDR blocks with a VPC was previously restricted to static CIDR configurations. We can now configure a VPC to dynamically associate secondary CIDR blocks allocated from IPAM.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request