appengine: Suppress null automatic_scaling blocks during Read #17905
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.
Fixes #17531
I went with this over O+C or a DSF because the field exists in a oneof (
scaling
in proto) and those options both preserve the set-but-deeply-nilautomatic_scaling
block in state, meaning we'd eventually send it to the server even if the user was sending a differentscaling
entry. This approach is worse if they start returning values for existing fields because it will break users again, but it's at least mitigatable with lifecycle.ignore_changes if that happens.Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#10476