Handle service account casing in google_bigquery_dataset_access #11875
+21
−0
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 hashicorp/terraform-provider-google#19547.
A follow-up to #11477. Service account names come back from the
GET
API in their original capitalization instead of being normalized to lower-case so need to be specifically handled.There isn't a good way to add a unit test organically since
google_service_account
only allows lower-case names and the error came from customers creating upper-case service accounts outside of Terraform.Release Note Template for Downstream PRs (will be copied)