From c8b1ec5af2d5cc1625a366ad64f20d958c0ab492 Mon Sep 17 00:00:00 2001 From: dtoro Date: Sat, 8 Aug 2026 21:48:17 +0200 Subject: [PATCH] =?UTF-8?q?0.28.2=20=E2=80=94=20widen=20api=20healthcheck?= =?UTF-8?q?=20start=5Fperiod=20to=2090s?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The api retries Infisical at startup (4x with backoff) before binding :8090. When Infisical is unreachable that adds ~60s, and the old start_period (10s) + 10 retries (~60s grace) ran out just before the bind — marking the api unhealthy and failing the deploy (nomos depends_on api-healthy). 90s covers the slow-startup window; the api genuinely serves /healthz once bound. --- VERSION | 2 +- docker-compose.yml | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/VERSION b/VERSION index 48f7a71..a37255a 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.28.1 +0.28.2 diff --git a/docker-compose.yml b/docker-compose.yml index fe0d6b0..76fb9f4 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -115,7 +115,10 @@ services: retries: 10 # Migrations and seed run before this container, but the first bind can # still take a moment; failures inside the start period don't count. - start_period: 10s + # The api also retries Infisical at startup (4x with backoff) before + # binding :8090 — when Infisical is unreachable that adds ~60s, so the + # start period must cover it or nomos (depends_on: api-healthy) fails. + start_period: 90s # Scheduler (Phase 3) — observe loop scheduler: