You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS now allows users to add auxiliary cidrs to the VPC to allow for expansion of the address space in the VPC. The following announcement from AWS details the funcitonality:
This issue has been automatically migrated to hashicorp/terraform-provider-aws#2841 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.
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.
ghost
locked and limited conversation to collaborators
Apr 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
AWS now allows users to add auxiliary cidrs to the VPC to allow for expansion of the address space in the VPC. The following announcement from AWS details the funcitonality:
https://aws.amazon.com/about-aws/whats-new/2017/08/amazon-virtual-private-cloud-vpc-now-allows-customers-to-expand-their-existing-vpcs/
Can the aws_vpc resource be updated to allow for additional CIDRs?
The text was updated successfully, but these errors were encountered: