Skip to content

Conversation

@ShadowCat567
Copy link
Contributor

@ShadowCat567 ShadowCat567 commented Jun 18, 2025

Description of changes

Gen1 CLI pushed some breaking changes when it released with the first SDK V2->V3 PR. This should update data to match those changes.
CLI PR: aws-amplify/amplify-cli#14199

This also updates the SSMClient we use from Gen1 CLI to be able to consume either a V2 or V3 style client, the V2 part should be removed in favor of the V3 client when this Gen1 CLI PR gets released (aws-amplify/amplify-cli#14238), but this allows us to operate with either while waiting for Gen1 CLI to release its changes.
Note: I used send to tell whether we are dealing with a V2 or a V3 client because V2 clients don't have send functions.

Unrelated to SDK Migrations
For some reason @types/node was set to Node 12 for a lot of the package.json files in this repo this includes an update that bumps them all to Node 18 because that is the version that is the best supported by this repo even though it was allegedly upgraded to Node 20.

Fixes FunctionTransformerTestsV2. Previously FunctionTransformer test would take the first account it found and use it as otheraccount. In a lot of cases this would be the account that is currently being used to run the test and would cause the test to fail. Added a check to ensure that otheraccount is not getting set to the account that is being used to run the test. -- this change was applied to Gen2 but it was never retroactively added to Gen1.

Issue #, if available N/A

Description of how you validated changes

Validated that the command amplify api add-graphql-datasource still works (as much as it can)
Validated that e2e tests still work properly in Gen1 CLI by running e2es on the SDK migrations branch that needs these changes and a branch that was based on dev with the only change being that it uses this PR's tag release as its @aws-amplify/amplify-category-api version.

Checklist

  • PR description included
  • yarn test passes
  • E2E test run linked
  • 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
  • Any CDK or CloudFormation parameter changes are called out explicitly

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

aws-amplify-bot added 3 commits June 19, 2025 15:06
@ShadowCat567 ShadowCat567 marked this pull request as ready for review August 8, 2025 18:19
@ShadowCat567 ShadowCat567 requested review from a team as code owners August 8, 2025 18:19
@ShadowCat567 ShadowCat567 changed the title Fix: Global Config Object in Data Gen1 Feat: Update Gen1 Data to be compatible with SDK v2->V3 migrations happening in Gen1 CLI Sep 16, 2025
svidgen
svidgen previously approved these changes Sep 16, 2025
@ShadowCat567 ShadowCat567 merged commit e642fdd into release-api-plugin-stable Sep 23, 2025
8 checks passed
@ShadowCat567 ShadowCat567 deleted the sdk-0 branch September 23, 2025 16:32
mrgrain pushed a commit that referenced this pull request Sep 25, 2025
…ppening in Gen1 CLI (#3310)

* fix: remove global config

* chore: update api

* v1.0.0

* Revert "v1.0.0"

This reverts commit 1aca077.

* fix: ssmclient can use v1 or v2

* chore: add ssm-client

* chore: update dep license

* fix: update expected error message

* chore: update node types

* chore: update node type for client-test-app

* chore: update jest to handle node: imports

* chore: upgrade jest

* chore: licenses

* Revert "chore: licenses"

This reverts commit 8e43f0e.

* Revert "chore: upgrade jest"

This reverts commit fa3dc3d.

* chore: change client-ssm version

* chore: license

* chore: update yarn lock

* chore: remove workaround

* fix: unit tests and better way of identifing v3 client

* chore: license

* chore: update v3 Client detection

* fix: search for other acc for FunctionTransformerV2 test like main does

---------

Co-authored-by: aws-amplify-bot <[email protected]>
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.

2 participants