Open Bug 1560669 Opened 6 years ago Updated 6 years ago

services should crash when started with insufficient config

Categories

(Taskcluster :: Services, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: dustin, Unassigned)

References

Details

We should prefer to crash early when config is not present or not correct.

I think we're inconsistent about this, and it leads to service deployments that look like they're working (process is running) but are actually completely nonfunctional.

The one case I know of is that auth will start without GCP credentials. We should follow up to fix that. Wander, is anything blocking doing so?

Otherwise, I think the easiest way to test this will be to do some experimenting with kubectl and see what doesn't crash.

Flags: needinfo?(wcosta)
Depends on: 1552970

I was tempted to WONTFIX this, since stuff pretty much does crash without config -- but the error messages are especially inscrutable.

I think I'll add something to the config library to allow cleanly asserting that configuration values are present with decent error messages.

(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #1)

The one case I know of is that auth will start without GCP credentials. We
should follow up to fix that. Wander, is anything blocking doing so?

Otherwise, I think the easiest way to test this will be to do some
experimenting with kubectl and see what doesn't crash.

Not that I know.

Flags: needinfo?(wcosta)

I found another one: tc-web-server will start up without JWT keys

Brian, can you mix this in with the deployment-config work you're doing?

Assignee: dustin → nobody
Flags: needinfo?(bstack)

Yep, I'll get it in today.

Flags: needinfo?(bstack)
Assignee: nobody → bstack
Status: NEW → ASSIGNED
Type: task → enhancement

I'll mix this into the planned deployment-configuration-updates work

Assignee: bstack → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(dustin)
You need to log in before you can comment on or make changes to this bug.