fix(idempotency): include sk in error msgs when using composite key #3709
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
idempotency
|
|
E2E tests for this branch are green: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/13784999706 |
phipag
approved these changes
Mar 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
This PR updates the
IdempotencyRecordclass so that it optionally accepts asortKeyparameter. This parameter is provided only when using theDynamoDBPersistenceLayerand when using a composite key (pk + sk).This fixes a bug that prevented the
IdempotencyAlreadyInProgressErrorandIdempotencyItemAlreadyExistsErrorfrom constructing the appropriate error message. Both errors now include both keys in the error message, making it easier for customers to detect idempotent requests or troubleshoot issues.Issue number: fixes #3691
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.