Remove use of google_kms_crypto_key_iam_binding
resources in acceptance tests to reduce test failures related to missing permissions
#6737
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.
Related to hashicorp/terraform-provider-google#16687
We have a group of bootstrapped KMS keys in the test projects that can be used by acceptance tests but aren't created/deleted by tests.
Because these resources are reused by tests there is a chance that tests will conflict with each other when editing the IAM permissions on the resource.
In this PR I remove unnecessary use of
google_kms_crypto_key_iam_binding
so it's easier to identify instances when a test is affecting bootstrapped resources' IAM policies authoritatively.An example I've identified that affects a bootstrapped KMS key is generated from the
mmv1/templates/terraform/examples/cloudfunctions2_cmek.tf.erb
file to make the generated testTestAccCloudfunctions2function_cloudfunctions2CmekExample
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#9590