-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
provider/google: Updated Read(..) behavior to handle deleted resources #3913
Conversation
b8cf1f1
to
122227e
Compare
Just one nitpick, otherwise LGTM - it would be probably more useful for potential debugging and reading crash logs in the future to replace the inline comment |
@radeksimko, good idea, I'll update that for all the Google resources. |
This is an awesome feature. would love to see it mainline. Actually got into a bit of a discussion with a coworker because I thought it was in mainline. |
122227e
to
b52c28c
Compare
b52c28c
to
cef0589
Compare
Fixes #4539 @radeksimko, I've added the logging, does it look good to you? |
@lwander This LGTM, merge at will once Travis passes |
|
provider/google: Updated Read(..) behavior to handle deleted resources
Woo! Thanks team! |
…x-pattern-set New Resource: aws_waf_regex_pattern_set
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
When Terraform discovers that a resource has been deleted on a Read, it should update the statefile accordingly. This behavior was pointed out by @apparentlymart in #3742 as the standard, and with this PR all GCP resources follow this convention.
@sparkprime