Fix permadiff of encryption_configuration in resource_bigquery_table when API returns an empty object #16926
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.
Sometimes the API returns a table with
"encryptionConfiguration": {}
when the input omits this field.Without this change, the Terraform state file would end up with
This would cause the subsequent plan to end up with a diff of
- encryption_configuration {} # forces replacement
.With this change, the new Terraform state file would have:
This would no longer result in a permadiff.
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#9757