Open PeppaTheC opened 4 months ago
Thanks for this feature request! If you are viewing this issue and would like to indicate your interest, please use the 👍 reaction on the issue description to upvote this issue. We also welcome additional use case descriptions.
This issue would be handled by the AWS Provider team at HashiCorp, so the request has been put into their backlog.
Thanks again!
Hi! Any updates?
| Value must be a valid KMS Key ID, got "" For clarity, I'm adding the example of KMS Key ID: "abjl6mft1vop****"
In versions under 1.6.0 we had an ability to use alternative S3-like backends (for example Yandex Storage) and alternative KMS-like services (Yandex KMS)
But now it is impossible to use new versions of terraform with yandex provider in such scenarios according to this issue
Terraform Version
Use Cases
Hi, we have our own s3 like storage to save terraform state.
Starting from
terraform version 1.6.0
there is a validation step forkms_key_id
field, here.And so, we have error
Attempted Solutions
There is no existing solution.
Proposal
Can we add new flag/parameter to s3 backend configuration to disable
kms_key_id
validation?References
No response