Remove use of google_kms_crypto_key_iam_binding
resource in tests, to make tests stable in overnight testing
#6745
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.
This PR will help address test failures like:
In this PR I remove
google_kms_crypto_key_iam_binding
from tests that use shared crypto keys. I have also removed that resource from tests that provision their own crypto keys to improve signal-to-noise when we need to solve this same problem again in future.This PR stops these tests affecting shared crypto keys:
Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#9621