feat: change to AWS SDK V3 #64
Merged
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
bflorian
force-pushed
the
aws-sdk-v3
branch
6 times, most recently
from
3d6c33f to
e622005
Compare
bflorian
changed the title
rossiam
approved these changes
Oct 2, 2023
|
|
||
| ### Partition Key Prefix | ||
|
|
||
| The default behavior is to construction the partition key of the context records from the installedAppId with |
There was a problem hiding this comment.
Minor grammar error here. construction -> construct.
github-actions bot
pushed a commit
that referenced
this pull request
Oct 2, 2023
## [2.2.0](v2.1.2...v2.2.0) (2023-10-02) ### Features * change to AWS SDK V3 and add get/set item to context ([#64](#64)) ([00e1a8b](00e1a8b))
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
BREAKING CHANGE: The initialization of the context store is not backward compatible since the AWS V3 client is initialized
differently than the V2 client. Otherwise, the operation of the context store is backward compatible with the 2.X version
This update uses the V2 version of the AWS DynamoDB SDK, which is more modular than the V2 version, which is being retired.