-
Notifications
You must be signed in to change notification settings - Fork 421
feat(idempotency): allow custom sdk clients in DynamoDBPersistenceLayer #2087
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
feat(idempotency): allow custom sdk clients in DynamoDBPersistenceLayer #2087
Conversation
Signed-off-by: heitorlessa <[email protected]>
Signed-off-by: heitorlessa <[email protected]>
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #2087 +/- ##
========================================
Coverage 97.45% 97.45%
========================================
Files 146 146
Lines 6748 6750 +2
Branches 477 478 +1
========================================
+ Hits 6576 6578 +2
Misses 136 136
Partials 36 36
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Walked @leandrodamascena through the changes in a peer review. Merging |
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.
LGTM!
Issue number: #2073
Summary
Changes
This PR adds a new constructor parameter
boto3_client
inDynamoDBPersistenceLayer
. This unblocks customers wanting to use DynamoDB Local, LocalStack, or AWS SDK Stubbers more cleanly (no private attribute access).It also unblocks the documentation PR where we're trying to provide an example of how to use DynamoDB Local for testing.
User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
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.