-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Allow aws_route_table_association import #5359
Allow aws_route_table_association import #5359
Conversation
Are there any plans to get this merged? Without this functionality I don't see any way of fully importing an existing VPC (except maybe editing my state file directly?). |
Is there a reason this isn't being merged? |
Would be nice to get this merged as I am currently facing the issue with importing RTAs |
As a work around, you can use something like terraforming (written in Ruby) to export AWS config as security groups then import these into TF state. Next, export TF state and parse for the actual values (state is json) and update your HCL/config. You could also dump with boto3 or any other SDK and generate the config then reconcile. The key is reconciling with tfstate after import. |
Seems like this was closed in another PR |
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! |
Fixes #561
Changes proposed in this pull request:
association_id
Output from acceptance testing: