Phase 5 — cutover plan (pre-staged; deploy held)#94
Closed
chrisbc wants to merge 1 commit into
Closed
Conversation
- docs/PHASE5_CUTOVER.md: in-place replacement, rollback (image-only, no new write shapes), differential validation via the built-in cli_ab_test (prod-vs-test, covers the full migrated surface), promote + 30-min watch, post-healthy legacy-cleanup scope - reuse cli_ab_test (no drive_live.py needed); in-process parity already locked by test_strawberry_parity.py - actual deploy/promote needs AWS creds + prod go-ahead Refs #86
This was referenced Jun 24, 2026
Member
Author
|
Landed via the combined PR #95 (one merge → one test-stage deploy, per runbook G7). Per-phase detail preserved here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked migration — PR 7 of N. Base =
migrate/strawberry-p4(Phase 4, #93).Epic: GNS-Science/nshm-toshi-api#359 · Tracking: #86
Pre-stages the cutover. No deploy here — the actual test-stage deploy,
cli_ab_test, and prod promote need AWS credentials + an explicit prod go-ahead.docs/PHASE5_CUTOVER.mdcli_ab_test(prod-vs-test) — it already covers the exact migrated surface, so nodrive_live.pyis needed (unlike the Model pilot). In-process parity is already locked bytest_strawberry_parity.py(11 differential checks).schema.py/Flask/handler.py, renamestrawberry_schema.py→schema.py, drop legacy deps. Ordered after cutover (the differential tests +CompositeRuptureSectionsdelegation still import graphene).Status
Engineering (Phases 0–4) complete and stacked: #88–#93. This PR + the deploy are the remaining steps; the deploy is yours to trigger.