google_storage_bucket
: fix custom_placement_config
values not normalized
#7551
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.
Resolves hashicorp/terraform-provider-google#18035
Solution was to use
StateFunc
which converts the values indata_locations
to be set as uppercase before storing into state. However as stated in the linked issue, there's a known problem with SDK that when usingStateFunc
in a nested attribute such astype.Set
it will add the new value instead of replacing.But by ignoring values in
data_locations
when expanding that aren't all capitalized, we can ensure that the final state will only include what we specified inStateFunc
test output:
TestAccStorageBucket_dualLocation_lowercase
- newly added testTestAccStorageBucket_dualLocation_versionChange
- newly added test to ensure that behavior for user doesn't change:TestAccStorageBucket_dualLocation
:Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#10936