-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/aws_dynamodb_table: Perpetual diff for encrypted replicas with default keys #27850
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v4.52.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
The problem here came from a sort of perfect storm:
The solutions (choose one):
|
Thanks a lot for the clear explanation, @YakDriver -- this helps a lot for reviewing changelogs when updating the provider in production! |
Hi, I'm still seeing this issue on 4.55 -- has this been fixed? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
N/A
AWS Provider Version
4.39.0
Affected Resource(s)
Expected Behavior
When a DynamoDB is created with replicas and encryption enabled with default keys, a perpetual diff is reported for the
kms_key_arn
Actual Behavior
No diff is reported
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform apply
terraform plan
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
May be related to #25812 and #26552
Would you like to implement a fix?
No response
The text was updated successfully, but these errors were encountered: