Rollback Plan: Frontend Pipeline Cutover

Per-Partition Rollback — Re-enable Auto-Build

If the GitHub Actions pipeline fails for a partition, re-enable Amplify’s auto-build to restore the previous branch-sync deployment model. The existing branch connections (dev→dev, stage→stage, prod→main) are unchanged — re-enabling auto-build immediately restores the old behavior.

Partition	Command
dev	aws amplify update-branch --app-id d38w5m1ngjza76 --branch-name dev --enable-auto-build --region us-east-1 --profile Alpha002-Admin
stage	aws amplify update-branch --app-id d1kbrvra79y8sc --branch-name stage --enable-auto-build --region us-east-1 --profile Alpha002-Admin
prod	aws amplify update-branch --app-id duhexavnwh88g --branch-name main --enable-auto-build --region us-east-2 --profile Admin-Alpha1

After re-enabling, push any commit to the corresponding branch (dev, stage, or main) to trigger an Amplify build.

Per-Partition Rollback — Trigger Manual Build from Original Branch

If auto-build is re-enabled but you need to force an immediate build without pushing a commit:

Partition	Command
dev	aws amplify start-job --app-id d38w5m1ngjza76 --branch-name dev --job-type RELEASE --region us-east-1 --profile Alpha002-Admin
stage	aws amplify start-job --app-id d1kbrvra79y8sc --branch-name stage --job-type RELEASE --region us-east-1 --profile Alpha002-Admin
prod	aws amplify start-job --app-id duhexavnwh88g --branch-name main --job-type RELEASE --region us-east-2 --profile Admin-Alpha1

Redeploy a Previous Commit via GitHub Actions

If the pipeline is working but a bad commit was deployed:

1. Go to: https://github.com/Arda-cards/arda-frontend-app/actions/workflows/redeploy.yaml
2. Click “Run workflow”
3. Select main branch
4. Choose the target partition
5. Enter a known-good commit SHA (from git log --oneline main)
6. Run the workflow

The workflow calls amplify start-job --commit-id {sha} which builds the specified commit from git — no artifact storage needed.

Emergency: Full Revert to Branch-Sync Model

If the GitHub Actions pipeline needs to be completely abandoned:

1. Re-enable auto-build on all three partitions (commands above)
2. The dev, stage, and main branches still exist and have not been modified
3. Push to each branch to trigger Amplify builds
4. The validate-pr-source.yml workflow still enforces the dev → stage → main promotion chain
5. Remove or disable the deploy.yaml and redeploy.yaml workflows on main

Contact List

Name	GitHub	Role
denisa	@denisa	Reviewer
jmpicnic	@jmpicnic	Reviewer, Operator
danmerb	@danmerb	Reviewer
davequinta	@davequinta	Reviewer

Decision Framework

Scenario	Action
Single partition fails, others work	Rollback that partition only; investigate
Multiple partitions fail with same error	Pause cutover; rollback all affected; investigate root cause
OIDC/IAM error	Check IAM trust policy; verify environment: subjects; check branch ref
Amplify build fails (not deployment)	Check build logs; likely env var or code issue, not pipeline issue
Site loads but API calls fail (401)	Check ARDA_API_KEY in Amplify env vars vs backend expectation