provider/google: Make google_compute_autoscaler use Update instead of Patch. #15101
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.
It looks like our vendored code thinks that Patch has "autoscaler" as an optional field, but the documentation suggests that it is required. It probably regressed when we vendored a new copy of the client code around a month ago.
We didn't catch this because the
_update
test didn't perform anUpdate
- it performed aDestroy
followed by aCreate
instead. This PR updates the tests so that an actualUpdate
is performed.Patch doesn't make much sense in this context - we pass in an entire copy of the resource, so we should be using Update anyways.
Fixes: #15056
@danawillow