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

Not able to specify assign_ipv6_address_on_creation for subnets #185

Closed
chrissam opened this issue Nov 2, 2018 · 3 comments
Closed

Not able to specify assign_ipv6_address_on_creation for subnets #185

chrissam opened this issue Nov 2, 2018 · 3 comments

Comments

@chrissam
Copy link

chrissam commented Nov 2, 2018

I don't find a way to specify assign_ipv6_address_on_creation for subnets in the vpc module, which is available as part of aws_subnet resource.

### Sample vpc config:

module "vpc" {
  source = "terraform-aws-modules/vpc/aws"
	version = "1.46.0"

  name = "${var.vpc_name}"
  cidr = "${var.vpc_cidr_block}"

  azs             = "${var.availability_zones}"
  private_subnets = "${var.private_subnets}"
  public_subnets  = "${var.public_subnets}"

  enable_nat_gateway = true
  enable_vpn_gateway = true

  assign_generated_ipv6_cidr_block = true
	assign_ipv6_address_on_creation = true

  tags = {
    Terraform = "true"
  }
}

Result:
Error: module "vpc": "assign_ipv6_address_on_creation" is not a valid argument

@sharath-yml
Copy link

I had the same issue. As a workaround, I forked this project into: https://github.com/sharath-yml/terraform-aws-vpc and added this option for myself. I will spend more time on this later, and probably raise a PR on this after some time.

@antonbabenko
Copy link
Member

v2.10.0 has been released (see #317).

@github-actions
Copy link

github-actions bot commented Nov 3, 2022

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants