feat: Grants output marked as sensitive data #33
Merged
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.
Description
When using grants for KMS keys, Terraform reports the following:
Therefore, adding the proper sensitive parameter to the grants output. The reason is that the grants expose a token that is considered to be sensitive.
Motivation and Context
This is related to this issue that was included in AWS provider version 5.51.0, where the grant_token output is marked as sensitive, and therefore as per Terraform error shows:
To reduce the risk of accidentally exporting sensitive data that was intended to be only internal, Terraform requires that any root module output containing sensitive data be explicitly marked as sensitive, to confirm your intent.
.Breaking Changes
No, in previous versions to 5.51.0 it will work fine, but in newer versions it won't.
How Has This Been Tested?
examples/*
projectspre-commit run -a
on my pull request