Fix settings.data_cache_config permadiff when set to false #8889
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[upstream:2936c3ba867221c9bfcdeb2a82b5542b0da91897] Signed-off-by: Modular Magician <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When settings.data_cache_config false a permadiff will result. This is due to the fact that CloudSQL API will not return data_cache_config when there is no data cache. Update terraform to match CloudSQL API by representing non existent data cache config as set to false .
Mentioned in:
hashicorp/terraform-provider-google#15227
hashicorp/terraform-provider-google#19144
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#12496