Clear startup error and exit code for a bad data store config #429

Closed
opened 2026-11-18 05:14:40 +00:00 by jcoffey-dev · 3 comments
Owner

K-S6 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)

The chart's pre-flight check and Kubernetes events need to tell 'can't reach PostgreSQL' from 'bad credentials' from 'bad config'.

Done when

  • Distinct log line and exit code per case, documented
**K-S6** · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts) The chart's pre-flight check and Kubernetes events need to tell 'can't reach PostgreSQL' from 'bad credentials' from 'bad config'. **Done when** - Distinct log line and exit code per case, documented
jcoffey-dev added this to the 27.1 milestone 2026-11-18 05:14:40 +00:00
jcoffey-dev added the enhancement label 2026-11-18 05:14:40 +00:00
jcoffey-dev self-assigned this 2026-11-18 06:28:58 +00:00
jcoffey-dev added the
priority
p2
label 2026-11-18 06:28:58 +00:00
Author
Owner

Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.

Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Author
Owner

Started: #472.

Started: #472.
Author
Owner

Done in #472: each data store failure at start-up now has its own first words and exit code. The docs are inbuxa/inbuxa.org#174, which ships with rc.32.

Done in #472: each data store failure at start-up now has its own first words and exit code. The docs are inbuxa/inbuxa.org#174, which ships with rc.32.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-server#429