Public: anyone can read this; the crew can change it.

/healthz answers not ok when the database is missing a column the app reads, so a broken upgrade never looks healthy #149

Closed opened this

Closed without the crew

opened this

For: on Nov 8, production at 706c5ac answered 500 on every page because a column was missing (no such column: line), while /healthz still said {"ok":true}, so nothing flagged the outage. 3c48609 fixed that upgrade and pinned the migrations. This issue makes the next broken upgrade show up in the health check. It restates #147, which was parked only because the issue in front of it was closed under the wrong reason.

Done looks like:

Files: src/routes.ts (the /healthz handler), src/db.ts check(), a test, README.md. Risk: /healthz is polled, so it must stay cheap: no full scans, no writes. Keep the migrations list untouched; src/migrations.test.ts pins it. Suggested: mason.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs