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

Add destination prefix list to route table #15273

Closed
gdavison opened this issue Sep 22, 2020 · 6 comments
Closed

Add destination prefix list to route table #15273

gdavison opened this issue Sep 22, 2020 · 6 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/ec2 Issues and PRs that pertain to the ec2 service.

Comments

@gdavison
Copy link
Contributor

gdavison commented Sep 22, 2020

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

In addition to the destination CIDR block (cidr_block) and destination IPv6 CIDR block (ipv6_cidr_block), Routes can support a destination prefix list ID. One of the destination values is required.

This is already implemented on the resource aws_route, but only as a Computed field. It does not exist for inline routes in aws_route_table or in the data source aws_route.

Affected Resources

  • aws_route_table
  • aws_route
  • data.aws_route_table
  • data.aws_route
@gdavison gdavison added the enhancement Requests to existing resources that expand the functionality or scope. label Sep 22, 2020
@ghost ghost added the service/ec2 Issues and PRs that pertain to the ec2 service. label Sep 22, 2020
@ewbankkit
Copy link
Contributor

@sethbacon
Copy link

Now that prefix lists are available, can we add them as a destination to the route resources in the list above? Any updates on this?

@randyspainhower
Copy link

any update on this? I need to do exactly this...

@puffpuf
Copy link

puffpuf commented Mar 18, 2021

Hey, any updates?

dmrzzz added a commit to techservicesillinois/aws-enterprise-vpc that referenced this issue Mar 27, 2021
NB: workaround for hashicorp/terraform-provider-aws#15273 requires re-running Terraform to update VPC route tables when a shared prefix list changes; fortunately for our purposes this should be rare.
@ewbankkit
Copy link
Contributor

All applicable PRs have been merged.
This functionality will be available with Terraform AWS Provider v3.35.0.

@ghost
Copy link

ghost commented Apr 29, 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 Apr 29, 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/ec2 Issues and PRs that pertain to the ec2 service.
Projects
None yet
Development

No branches or pull requests

5 participants