Skip to content

feat(gen2-migration): add decommission step to e2e test flow#14793

Draft
sai-ray wants to merge 1 commit intogen2-migrationfrom
sai/e2e-decommission-step
Draft

feat(gen2-migration): add decommission step to e2e test flow#14793
sai-ray wants to merge 1 commit intogen2-migrationfrom
sai/e2e-decommission-step

Conversation

@sai-ray
Copy link
Copy Markdown
Contributor

@sai-ray sai-ray commented Apr 21, 2026

Description of changes

Wire gen2-migration decommission into the E2E migration flow so every run exercises the full lifecycle including Gen1 teardown.

Issue #, if available

#14790

Description of how you validated changes

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.

@sai-ray sai-ray changed the title feat(amplify-gen2-migration-e2e-system): add decommission step to feat(gen2-migration): add decommission step to e2e test flow Apr 22, 2026
@sai-ray sai-ray force-pushed the sai/e2e-decommission-step branch from 220c359 to f8b4137 Compare April 22, 2026 20:46
E2E migration flow

Wire `gen2-migration decommission` into `App.migrate()` so the
E2E system exercises the full migration lifecycle including Gen1
teardown. After the final `testSharedData()`, the flow checks out
the Gen1 branch, runs `amplifyPullNonInteractive` to restore
`amplify-meta.json` (which is gitignored and missing after branch
switch), then runs `decommission` and verifies the Gen2 app still
works via `testGen2()`.

The `decommission()` method follows the same pattern as the
existing `refactor()` — delegates to `runMigrationStep()` with
no extra args. The `amplifyPullNonInteractive` call reads the
appId from `team-provider-info.json` (which is tracked in git).

Apps with `skipRefactor=true` are unaffected since the new calls
live after the early return in `migrate()`.

E2E runs confirmed the wiring works: `backend-only` and
`store-locator` completed the full flow including decommission
and post-decommission `testGen2`.
---
Prompt: Add decommission step to E2E migration flow after
refactor, followed by testGen2() to verify the Gen2 app is
self-contained after Gen1 teardown. Run E2Es on all 9 apps
in parallel.
@sai-ray sai-ray force-pushed the sai/e2e-decommission-step branch from f8b4137 to 79f03ae Compare April 23, 2026 03:05
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.

1 participant