Open magreenbaum opened 1 year ago
Hi @magreenbaum thanks for reporting this.
It appears this is an oddity in the underlying implementation. AWS treats the KMS key being set to AWS_OWNED_KMS_KEY
the same as the field not being set. When it's read back from AWS, if it's managed by AWS it's not set to AWS_OWNED_KMS_KEY
but is always not set. API Reference
This issue can be avoided by just not setting the field if you want it to be managed by AWS.
This might be worth logging as an issue for the underlying terraform provider as I expect that is where it would need to be addressed then would be available in the next release of our provider once fixed on their side.
I've opened an issue with the terraform provider. https://github.com/hashicorp/terraform-provider-aws/issues/31403
What happened?
The QLDB ledger module
kms_key
input shows a continual diff to addkms_key
.Expected Behavior
kmsKey
applies and no longer shows a diff to be added on each subsequentpreview
orup
.Steps to reproduce
Run
pulumi up
using this code snipped. Then run subsequentpreview
orup
.Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).