KMS: add google_kms_crypto_key_versions data source
#8026
Merged
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:4e9aa4fd7d591cb006f340641b1bf0f95e0a91db] Signed-off-by: Modular Magician <[email protected]>
modular-magician
deleted the
downstream-pr-4e9aa4fd7d591cb006f340641b1bf0f95e0a91db
branch
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.
continuation of GoogleCloudPlatform/magic-modules#11381
splitting up into two parts
This is the first step which addresses adding a plural data source for
cryptoKeyVersionKeeping in draft untilpurposeis added in. All other fields are supported.Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#11455