-
Notifications
You must be signed in to change notification settings - Fork 184
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
Migration to AWS SDK v3 #641
Comments
Following! @abetomo Are you doing any of the work on this? |
I am planning to work on it soon, but not at this time. |
@abetomo when will you complete the migration to v3? |
motdotlaGH-641 This is still an experimental migration. First, only CreateFunction will be migrated. We also plan to maintain unit tests.
Please wait a moment as we proceed with the migration. |
GH-641 This is still an experimental migration. First, only CreateFunction will be migrated. We also plan to maintain unit tests.
Change to async/await style. Prepare to change to SDK v3. motdotlaGH-641
https://aws.amazon.com/jp/blogs/developer/announcing-end-of-support-for-aws-sdk-for-javascript-v2/
|
motdotlaGH-641 This is still an experimental migration. First, only CreateFunction will be migrated. We also plan to maintain unit tests.
motdotlaGH-641 All lambda clients have been replaced by v3. The next step is to replace other AWS resources with v3 as well.
The following note was displayed.
The text was updated successfully, but these errors were encountered: