-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Terraform import for aws_route_table should not import dynamic routes #5125
Comments
Hi @m4ce 👋 Sorry you were running into this unexpected behavior -- it turns out this was very recently addressed in #5100 which landed in master and will release with version 1.27.0 of the AWS provider, likely middle of this week. For the very latest updates, you can double check the AWS provider CHANGELOG. |
This has been released in version 1.27.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
Thanks @bflad ! |
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! |
This issue was originally opened by @m4ce as hashicorp/terraform#18418. It was migrated here as a result of the provider split. The original body of the issue is below.
When running a terraform import to import a routing table, dynamic routes that get propagated via a virtual private gateway are also imported.
This is problematic as those routes will not have an equivalent resource in terraform. As a result, terraform will try to delete these routes on subsequent runs.
The text was updated successfully, but these errors were encountered: