feat(gen2-migration): amplify-migration-system executes e2e flow for amplify init, using atmosphere credentials or local profile

[iankhou]

Description of changes

This is a CLI. See log example at the end.

Set up configurations for each sample app and configuration loaders. Introduce classes that can execute Amplify deployments either locally or to Atmosphere.

Using Atmosphere is only supported in CI, or by developers in the team with the correct permissions. You must have a .gamma.env file with properly configured variables according to the README IN ADDITION to permissions on your AWS account.

You must specify a profile using --profile.

About 40% of this change is tests.

Description of how you validated changes

Unit tests.

Used atmosphere endpoint to run integration and e2e tests that run amplify init. Deployed amplify apps using this CLI to my personal dev account using profiles under different names, and also the default profile on my system.

Ran a local deployment using a profile with AmplifyAdmin IAM permissions. See log example at the end.

Next steps

• Category addition logic
• Author an e2e test that and adds all categories (after amplify init)
• Author an e2e test that runs amplify init, adds categories

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

Log example

Note that I manually set my amplify binary, as I was using the CLI built by the monorepo during development and don't have Amplify CLI installed globally. If you do, you may just run something like:

yarn migrate --app project-boards --profile amplify1

$ export AMPLIFY_PATH=/Users/ianhou/workplace/amplify-cli/.bin/amplify-dev && yarn migrate --app project-boards --profile amplify1


╔══════════════════════════════════════════════════════════════╗
║                                                              ║
║           AWS Amplify Gen1 to Gen2 Migration System          ║
║                                                              ║
║  Automation for migrating Amplify applications from          ║
║           Gen1 to Gen2                                       ║
║                                                              ║
╚══════════════════════════════════════════════════════════════╝

[2026-02-10T00:08:28.059Z] [INFO]  Local environment detected - will use local AWS profile: amplify1 for credentials
[2026-02-10T00:08:28.064Z] [INFO]  Discovered 6 available apps: discussions, fitness-tracker, media-vault, product-catalog, project-boards, project-boards-backend-only
[2026-02-10T00:08:28.065Z] [INFO]  Selected app: project-boards
[2026-02-10T00:08:28.065Z] [INFO]  File logging set: /var/folders/zy/p394g9w14sbbfwj23q2pd3f00000gq/T/amplify-gen2-migration-e2e-system/logs/260209190828065ards.log
[2026-02-10T00:08:28.067Z] [INFO]  [app:project-boards] Successfully loaded configuration for project-boards
[2026-02-10T00:08:28.067Z] [INFO]  [app:project-boards|op:initializeApp] Starting initialization for project-boards with deployment name: 260209190828065ards
[2026-02-10T00:08:28.068Z] [INFO]  [app:260209190828065ards|op:createAppDirectory] Creating app directory for 260209190828065ards
[2026-02-10T00:08:28.069Z] [INFO]  [app:260209190828065ards|op:createAppDirectory] Successfully created app directory: /var/folders/zy/p394g9w14sbbfwj23q2pd3f00000gq/T/amplify-gen2-migration-e2e-system/output-apps/260209190828065ards
[2026-02-10T00:08:28.100Z] [INFO]  [app:260209190828065ards|op:initializeApp] Starting amplify init for 260209190828065ards (config: project-boards)
[2026-02-10T00:09:09.216Z] [INFO]  [app:260209190828065ards|op:initializeApp] Successfully initialized Amplify app in /var/folders/zy/p394g9w14sbbfwj23q2pd3f00000gq/T/amplify-gen2-migration-e2e-system/output-apps/260209190828065ards, 260209190828065ards (took 41115ms)
[2026-02-10T00:09:09.217Z] [INFO]  Stopping before category processing as per current implementation scope

Related to #14537

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

[iankhou]

Rename to amplify-migration-e2e-system
Move to packages/ directory

[iankhou]

Rename package.json task dev -> migrate

[iankhou]

Don't use require(), use import instead. clean up all mocks using jest resetAllMocks

[iankhou]

Add necessary logs from nexpect to dumpfile

[iankhou]

deleteAmplifyApp should wait until resources are deleted. poll until root stack is gone. aws sdk, import sdk cloudformation client called waitforstackstatus, deleted.

[iankhou]

default to default profile in the CLI.

[iankhou]

directory manager integration test doesn't need to be named integration test. only if it does a network call.

[iankhou]

make the suffix of the deployed app names similar to the amplify-migration-apps name

[iankhou]

Remove verify-app validation.

[iankhou]

Remove validations from list-apps

[iankhou]

some apps are not neccesarily react, parameterize this.

[iankhou]

make profile argument required.

[iankhou]

for atmosphere flow, create a profile with session token, config and credentials files

[iankhou]

remove multi-app deployment functionality, make it take a single app.

[iankhou]

some apps are not neccesarily react, parameterize this.

This is now configurable in migration-config.json, under app.framework.

[iankhou]

default to default profile in the CLI.

Made it required. Either --profile or --atmosphere must be indicated.