cutover-prep: execute end-to-end rehearsal in staging

Open
#54 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
ci-cd, devops, infrastructure, testing

Research direction

Read plans/cutover-prep.md and check dependency #36 before starting. Once staging is operational, run script:cutover-dry-run and work through every listed rehearsal, validation, monitoring, snapshot, and review check; done means all checklist items are verified and ticked.

Written by the indexing model from the issue text.

Description

Several validation criteria from plans/cutover-prep.md require a live staging cluster + bucket + Slack workspace to verify. They were left unchecked at merge of #53 because the cluster isn't stood up yet (tracked by #36).

Once the staging cluster is operational, run through and tick these:

  • Dry-run script (script:cutover-dry-run) runs end-to-end against the staging cluster + bucket without errors
  • 100 sample laddr URLs all resolve correctly via legacy-id redirects on the staging deployment
  • SAML assertion for a test laddr user matches their pre-cutover NameID byte-for-byte
  • Account-claim flow works for: email-match user, password-match user, dead-email user (staff-review path)
  • Rollback procedure rehearsed at least once: bring up staging, simulate cutover, then "rollback" (DNS flip) and verify the legacy site still works
  • Cutover runbook reviewed by at least one staff member who hasn't been deep in the code
  • Post-cutover monitoring alarms verified by intentionally breaking /api/health in staging
  • Snapshot CI workflow has actually run on schedule against the production data repo and produced a valid scrubbed branch
  • Snapshot clones + boots a fresh dev API (STORAGE_BACKEND=filesystem, empty private storage)

Depends on: #36 (cluster stand-up). Blocks: the actual cutover event.

Dominant language
TypeScript
Stars
1
Forks
1
Avg merge
1d 20h
Merged PRs (30d)
25

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForPhilly/codeforphilly-ng

All issues in CodeForPhilly/codeforphilly-ng

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.