Phase 4 — deploy/CI/deps hardening (clean pass)#93
Closed
chrisbc wants to merge 1 commit into
Closed
Conversation
- container: amd64 build green with migrated deps; 360MB (< 500MB aim, no multi-stage); Mangum handler + full schema import in-image - pip-audit runtime deps: no known vulnerabilities - plugin chain (s3rver + serverless-dynamodb) loads; no resolutions needed - drop dead serverless-wsgi npm plugin + stale requirements_* scripts; yarn lockfile updated, --immutable clean (§4.6) - memory stays 2096; CI already on -uv test+deploy workflows 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 6 of N. Base =
migrate/strawberry-p3(Phase 3, #92).Epic: GNS-Science/nshm-toshi-api#359 · Tracking: #86 · Log:
docs/MIGRATION_LOG.mdThe deploy-layer validation. Came back clean — the migration's deps/container/CI are healthy.
Findings
docker buildgreen with the migrated deps (strawberry/fastapi/mangum in, pynamodb out). Image 360 MB (geo stack) — under the §A3 500 MB aim, so single-stage stays.docker run … import solvis_graphql_api.app→ Mangum handler + full Strawberry schema load in-image. Dep path: the shareddeploy-to-aws-uv.ymlexportsrequirements.txtfromuv.lockbefore the build (local build mirrors it).s3rver+serverless-dynamodbload fine; noresolutionsblock needed — solvis doesn't hit the fast-xml-parser/s3rver clash toshi-api did.pip-auditon runtime deps → none. Nopyupbump.Changes
serverless-wsginpm plugin (no longer inserverless.yml) + stalerequirements_1/2scripts frompackage.json;yarn install --mode update-lockfilethen--immutableclean (§4.6).Verification
pip-auditclean; plugin chain loads;yarn install --immutableclean-uvtest + deploy workflows