-
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
aws_route import reports success even on fail #6404
Comments
This should be fairly easy to fix. I'll submit a PR to address it shortly. |
Hey @YakDriver 👋 This line:
Is handed upstream in Terraform core after the Given we often use Given the above, I'm going to close this issue for now since there is nothing we can change in the provider itself for this behavior beyond calling |
Hey @bflad, I think we can find a middle path where we're not performing a full-on read but checking for the routes existence before calling the import a success. |
This was fixed upstream (hashicorp/terraform#20018) and will be part of the next Terraform Core release (0.12.4). 😄 |
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
Terraform Version
Terraform v0.11.10
AWS v1.43.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
It should fail on import.
Actual Behavior
It displays
Import complete!
and then fails on refresh, which is confusing.Steps to Reproduce
After creating the resources, remove the route and attempt to import a non-existent route:
Important Factoids
References
The text was updated successfully, but these errors were encountered: