Send empty GKE objects explicitly #8400
Merged
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.
This change is mainly just to correct some currently misleading code- 2/3 of these fields are Computed and can't actually trigger this check (at least in reasonable circumstances) and
linux_node_config
still has a permadiff afterwards. This does mean that updates that removelinux_node_config
that also include other changes will move on to the other changes so it at least has some user benefit, in addition to stopping the misleading snippet from propagating. This could be valid for some blocks, just not the one where is still happens!Followup to GoogleCloudPlatform/magic-modules#11971
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#11978