aws_vpc secondary cidr block

[benrobinsonsonos]

Affected Resource(s)

• aws_vpc

Terraform Configuration Files

resource "aws_vpc" "vpc" {
  cidr_block = "10.0.0.0/16"
  secondary_cidr_blocks = ["10.2.0.0/16"]
}

Expected Behavior

Attach secondary CIDR block to VPC.

Actual Behavior

secondary_cidr_blocks is not a supported argument for resource aws_vpc.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply

Important Factoids

AWS announced support for secondary cidr blocks in August 2017. Argument should accept a list of cidr blocks.

References

https://aws.amazon.com/about-aws/whats-new/2017/08/amazon-virtual-private-cloud-vpc-now-allows-customers-to-expand-their-existing-vpcs/

https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html#vpc-resize

[ewbankkit]

Implemented in #1568.

[bflad]

A new aws_vpc_ipv4_cidr_block_association resource (instead of inline on the aws_vpc resource) has been merged into master and will be released with version 1.26.0 of the AWS provider, likely middle of next week. 🎉

[Hitesh-Agrawal]

Waiting for this feature.

[ghost]

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!