SCRUM-97: Healthcheck + restart-on-unhealthy for fulfillr containers #7
Reference in New Issue
Block a user
Delete Branch "scrum-97/fulfillr-healthcheck"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Self-heals the power-cycle failure where go-fulfillr's gated routes (newsletter/outreach/cases) 404 because a transient boot-time HMAC Secrets Manager fetch left them unregistered, with the process still up so nothing restarts it.
fulfillr.yml+fulfillr-dev.yml: add a podman healthcheck on thecontainers.podman.podman_containertask —wgetthe new dependency-free/api/v1/health/startupprobe (busybox wget ships in the alpine image),interval 30s / timeout 5s / retries 3 / start_period 30s(covers the ~14s HMAC retry backoff so a healthy boot is never flagged), andhealthcheck_failure_action: restart(--health-on-failure=restart) so podman restarts the container in place when those routes failed to register. Existingrestart_policy: on-failure:3kept (process-exit case).main.yml: bumpfulfillr+fulfillr-devimage →20260628.1930(the go-fulfillr build that adds/health/startup, SCRUM-97 PR #21, merged).Deploy after merge:
make deploy TAGS=fulfillr-dev(verifypodman inspect ... Health.Status=healthy), thenmake deploy TAGS=fulfillr.🤖 Generated with Claude Code