| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
health_check previously returned JsonResponse(data) unconditionally, so the ECS container healthcheck (curl -f) and any future smoke gate would false-green a container with a dead DB/ES/Redis/telemetry connection. Also exposes git_sha so a deploy can verify the running code matches what was just pushed.
Follows the same ARG->ENV pattern the container already uses for other build-time config. Feeds health_check's new git_sha field.
Generating migration files at deploy time instead of using committed ones is unsafe under a rolling deployment (briefly 2 tasks live) and means the schema that lands in prod was never reviewed. migrate itself stays here for now; moving it to an explicit one-off step is next.
| Back | FazBrowse Home | New Git URL |
Summary
First slice of the ECS CD-pipeline work (Phase 0+1 of the plan). Independent value on its own — fixes two real bugs found while auditing deploy-to-ecs.yml.
Test plan
Next in this series
Moving migrate out of the entrypoint into an explicit ECS one-off task, fixing deploy-to-ecs.yml's if: always() and fragile infra-change condition, wiring a smoke-test gate, and adding rollback-on-failure — tracked as follow-up PRs.