Closed tom-noble closed 3 years ago
Any updates on this?
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Reproduction Steps
What did you expect to happen?
Since a new table is created as part of the update, I expected the new table to be automatically replicated and the deployment to succeed.
What actually happened?
CDK attempts to create a new table with the new partition key but a replica is not created. This causes the DynamoDBReplica custom resource to hang in the UPDATE_COMPLETE_CLEANUP_IN_PROGRESS state.
This eventually fails the deployment due to timeout
Environment
Other
I think the reason this happens is that despite creating a new table the event is marked as an Update (shown below).
The code generated by CDK to handle DynamoDB replication only checks for Create and Delete events, so a replica isn't created (shown below).
This is reinforced by the fact that deleting and rebuilding the stack fixes the issue. CDK attempts to Create the table from scratch, rather than Update an existing one, and a replica is created successfully. If I update the partition key of the table again, I expect to run into this issue again.
This is :bug: Bug Report