provider/google: Move 404 checking into a function in provider.go, call it from instance and IGM #14190
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial PR for #13943. It fixes the specific concern by adding in 404 checking for
resource_compute_instance_group_manager
, and also shows the new function being reused inresource_compute_instance
(note that it also exposed a bug- if there is a 404, we should returnnil
instead of an error). If this looks good, I'll check it in and then open up a separate PR for the rest of the resources.