fix(smoke): load staging env before migration/gameplay checks #140

2026-02-28T17:35:51+01:00

dev-bot commented

2026-02-28 17:35:51 +01:00

Summary

load /etc/wpp/staging.env (or $ENV_FILE) before manage.py migrate --check and manage.py smoke_staging in staging smoke suite
keep smoke logic unchanged otherwise; only env bootstrap for DB/schema parity

Why

Staging smoke can fail with schema mismatch when manage.py commands run without staging DB env, which makes checks read a different DB context after failed/partial deploy paths. This is a low-risk hardening directly for #130 and release-readiness #90.

Checks

bash -n infra/staging/smoke_suite.sh
.venv/bin/python manage.py check
.venv/bin/python manage.py test lobby.tests.SmokeStagingCommandTests.test_smoke_staging_command_runs_full_flow

Refs #130
Refs #90

## Summary - load `/etc/wpp/staging.env` (or `$ENV_FILE`) before `manage.py migrate --check` and `manage.py smoke_staging` in staging smoke suite - keep smoke logic unchanged otherwise; only env bootstrap for DB/schema parity ## Why Staging smoke can fail with schema mismatch when manage.py commands run without staging DB env, which makes checks read a different DB context after failed/partial deploy paths. This is a low-risk hardening directly for #130 and release-readiness #90. ## Checks - `bash -n infra/staging/smoke_suite.sh` - `.venv/bin/python manage.py check` - `.venv/bin/python manage.py test lobby.tests.SmokeStagingCommandTests.test_smoke_staging_command_runs_full_flow` Refs #130 Refs #90

dev-bot added 1 commit 2026-02-28 17:35:51 +01:00