Upgrade AWS SDK DynamoDB from v2 > v3 #2062
Open
+2,397
−358
Conversation
This file contains 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
|
lailien3
force-pushed
the
feature/iwtf-3449-aws-v2-to-v3
branch
from
fa9f84a
to
edd306a
Compare
lailien3
force-pushed
the
feature/iwtf-3449-aws-v2-to-v3
branch
from
780efb8
to
c8bf535
Compare
lailien3
force-pushed
the
feature/iwtf-3449-aws-v2-to-v3
branch
from
b0adb0e
to
b806cb0
Compare
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.
https://eaflood.atlassian.net/browse/IWTF-3449
This ticket is part of upgrading rod-licensing from using the AWS SDK v2 to v3.
This ticket specifically covers upgrading the parts of our codebase that use the AWS SDK to use DynamoDB
(NOT SecretsManager, S3 or SQS yet)
We expect this to be the largest and most complex bit of the SDK upgrade.