-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to configure IPAM exclusively for IPv4 or IPv6 #1153
Comments
3 tasks
@Vinoth-S15 I prepared #1155 with changes in module and example. Are you able to take a quick look , if it's ok for you , please ? |
@sebastianczech The changes are satisfactory to me. |
Vinoth-S15
changed the title
The ability to configure IPAM exclusively for IPv6.
Ability to configure IPAM exclusively for IPv4 or IPv6
Jan 6, 2025
@bryantbiggs , are you able to take a look on this PR #1155 , please ? |
@bryantbiggs are you able to have a look on this PR #1155, please ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your request related to a problem? Please describe.
The current implementation of the aws_vpc resource does not provide the flexibility to independently use an IPAM pool for IPv4 and IPv6. In cases where IPAM is needed exclusively for IPv6 CIDR allocation, the configuration becomes inefficient and restrictive
Describe the solution you'd like.
To enhance flexibility, the assign_generated_ipv6_cidr_block argument should be updated to use the condition var.ipv6_ipam_pool_id == null instead of !var.use_ipam_pool. This change would allow IPAM to be configured specifically for IPv6 without impacting IPv4.
Additional context
The text was updated successfully, but these errors were encountered: