-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
DynamoDB: fix GlobalSecondaryIndexes parity in Create and DescribeTable #12119
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
Conversation
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 28m 38s ⏱️ - 1h 24m 22s Results for commit 34d894e. ± Comparison against base commit 630b2a1. This pull request removes 2872 and adds 2 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice fix 👍 ! LGMT ✔️
Co-authored-by: Giovanni Grano <[email protected]>
Do you know when it will be included in 4.x? |
Hello @nicolaschambrier, we have a minor release planned for the end of January (tentative 30th of January), so it will be available in a tagged release by then. Hopefully that works for you! |
Motivation
As reported in #12014, we've had a regression in our handling of GlobalSecondaryIndexes, probably due to the update of DDB-local from v1 to v2.
This really broke some users setup with Terraform, causing it to try to redeploy and fail.
I confirmed that with this fix, deploying the Terraform file and trying to applying it again do not fail anymore.
fixes #12014
Changes
GlobalSecondaryIndexes
depending on theBillingMode
CreateTable
andDescribeTable
by adding the missing fields to the responses