Skip to content
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

subnet_mapping block under aws_lb is missing the ipv6_address option #17150

Closed
shayisrael opened this issue Jan 17, 2021 · 2 comments · Fixed by #17229
Closed

subnet_mapping block under aws_lb is missing the ipv6_address option #17150

shayisrael opened this issue Jan 17, 2021 · 2 comments · Fixed by #17229
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Milestone

Comments

@shayisrael
Copy link

shayisrael commented Jan 17, 2021

Hi,

I've noticed that according to TF latest documentation here:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb#subnet_mapping

The only supported parameters inside the subnet_mapping block of aws_lb are : subet_id, allocation_id and private_ipv4_address.
However, in a network load balancer with dualstack ip_address_type - there should be also the possibility to set an ipv6 from the subnet IPv6 CIDR.

See the IPv6Address option here in AWS documentation: https://www.google.com/search?rlz=1C1GCEA_enIL876IL877&ei=qWgEYIKfLYiRsAfzxaEo&q=aws+subnet_m+mappngload+balancer+ipv6addrees&oq=aws+subnet_m+mappngload+balancer+ipv6addrees&gs_lcp=CgZwc3ktYWIQAzoECAAQR1CGFVjaSWDXSmgCcAN4AoABogmIAYdHkgEJMi0xLjYtMS43mAEAoAEBqgEHZ3dzLXdpesgBCMABAQ&sclient=psy-ab&ved=0ahUKEwjCl6CwtKPuAhWICOwKHfNiCAUQ4dUDCA0&uact=5

Can ipv6_address option also be added to the TF AWS provider please?

Thanks,
Shay

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

New or Affected Resource(s)

  • aws_lb

Potential Terraform Configuration

resource "aws_lb" "example" {
  name               = "example"
  load_balancer_type = "network"
  ip_address_type = "dualstack"
  subnet_mapping {
    subnet_id     = aws_subnet.example1.id
    allocation_id = aws_eip.example1.id
    ipv6_address = "2001:0db8:3c4d:0015:0000:d234::3eee:0001"
  }

  subnet_mapping {
    subnet_id     = aws_subnet.example2.id
    allocation_id = aws_eip.example2.id
    ipv6_address = "2001:0db8:3c4d:0015:0000:d234::3eee:0002"
  }
}

References

  • #0000
@shayisrael shayisrael added the enhancement Requests to existing resources that expand the functionality or scope. label Jan 17, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jan 17, 2021
@ghost ghost added the service/elbv2 Issues and PRs that pertain to the elbv2 service. label Jan 17, 2021
bill-rich added a commit that referenced this issue Jan 22, 2021
Add support for IPv6 subnet mapping to the aws_lb resource.

Resolves #17150
@bill-rich bill-rich removed the needs-triage Waiting for first response or review from a maintainer. label Jan 22, 2021
@github-actions github-actions bot added this to the v3.27.0 milestone Feb 4, 2021
@ghost
Copy link

ghost commented Feb 5, 2021

This has been released in version 3.27.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

@ghost
Copy link

ghost commented Mar 7, 2021

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Mar 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants