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

aws_vpc data source multiple cidr blocks #5481

Closed
ghost opened this issue Aug 8, 2018 · 3 comments
Closed

aws_vpc data source multiple cidr blocks #5481

ghost opened this issue Aug 8, 2018 · 3 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@ghost
Copy link

ghost commented Aug 8, 2018

This issue was originally opened by @adubkov as hashicorp/terraform#18635. It was migrated here as a result of the provider split. The original body of the issue is below.


Currently aws_vpc data source doesn't return multiple cidr blocks, just first one, which does discover current vpc address spaces difficult.

It would be nice to have such option since vpc can actually have multiple cidr blocks.

Terraform Version

Terraform v0.11.7
+ provider.aws v1.30.0
@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service. labels Aug 8, 2018
@ewbankkit
Copy link
Contributor

The additional VPC CIDR blocks can be obtained from the cidr_block_associations.cidr_block attribute.
This was added in #5098.

@github-actions
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Jul 29, 2020
@ghost
Copy link
Author

ghost commented Sep 29, 2020

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 Sep 29, 2020
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/ec2 Issues and PRs that pertain to the ec2 service. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

2 participants