-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Comments
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? |
any update on this? I need to do exactly this... |
Hey, any updates? |
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.
All applicable PRs have been merged. |
require it, and remove previous workaround for hashicorp/terraform-provider-aws#15273
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! |
Community Note
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 aComputed
field. It does not exist for inline routes inaws_route_table
or in the data sourceaws_route
.Affected Resources
The text was updated successfully, but these errors were encountered: