Skip to content

Dismantling global config object from SDK V2 #14199

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

Merged
merged 35 commits into from
Jun 19, 2025
Merged

Conversation

ShadowCat567
Copy link
Contributor

@ShadowCat567 ShadowCat567 commented May 6, 2025

Description of changes

This is in preparation of SDK V2 to V3 migrations changes (nothing has actually be migrated yet).
SDK V2 reaches end of life on September 8, 2025 and we must upgrade SDK to V3 before that happens: https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-javascript-v2/
SDK V2 has a global configuration object that can be used to store a configuration which is automatically loaded into all of the service objects that are created unless the service object specifies an alternate configuration when it is created.
This global configuration object does not exist in SDK V3 so this PR works to move all the work that used to be done by the global config object to each of the individual service objects.

The threshold for the size of all the binaries has also temporarily been raised.

Global Config must remain around for some Aurora DB utilities on the Data side, can be completely removed when the PR on the data side is merged and released.
Sibling PR in the data repo handles dismantling of the global config that data inherited from CLI: aws-amplify/amplify-category-api#3310

Description of how you validated changes

Did a combination of manual testing (ensured that proxies and credentials with Access Keys and Profiles works as well as add, push, and delete commands) and updating the current tests to ensure that they could work without the global sdk config.
Ensured that SSO credentials workaround still works:
image

Checklist

  • PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)
  • New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
  • Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

aws-amplify-bot and others added 9 commits May 7, 2025 11:27
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - amplify-dotnet-function-runtime-provider@2.1.5-sdk-v2-with-data-0.0
 - @aws-amplify/amplify-dotnet-function-template-provider@2.7.5-sdk-v2-with-data-0.0
 - [email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - amplify-java-function-runtime-provider@2.3.52-sdk-v2-with-data-0.0
 - @aws-amplify/[email protected]
 - amplify-nodejs-function-runtime-provider@2.5.30-sdk-v2-with-data-0.0
 - @aws-amplify/amplify-nodejs-function-template-provider@2.10.15-sdk-v2-with-data-0.0
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - amplify-python-function-runtime-provider@2.4.52-sdk-v2-with-data-0.0
 - [email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
…sh tagged release sdk-v2-with-data-0"

This reverts commit 5c4c686.
@ShadowCat567 ShadowCat567 marked this pull request as ready for review June 5, 2025 19:53
@ShadowCat567 ShadowCat567 requested a review from a team as a code owner June 5, 2025 19:53
sobolk
sobolk previously approved these changes Jun 16, 2025
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
 - [email protected]
 - [email protected]
 - [email protected]
 - @aws-amplify/[email protected]
 - @aws-amplify/[email protected]
@ShadowCat567 ShadowCat567 merged commit 72db54e into dev Jun 19, 2025
5 checks passed
@ShadowCat567 ShadowCat567 deleted the sdk-migrations-0 branch June 19, 2025 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants