services should crash when started with insufficient config
Categories
(Taskcluster :: Services, enhancement)
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.
| Reporter | ||
Comment 1•6 years ago
|
||
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.
Updated•6 years ago
|
| Reporter | ||
Comment 2•6 years ago
|
||
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.
Comment 3•6 years ago
|
||
(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 withkubectland see what doesn't crash.
Not that I know.
| Reporter | ||
Comment 4•6 years ago
|
||
I found another one: tc-web-server will start up without JWT keys
| Reporter | ||
Comment 5•6 years ago
|
||
Brian, can you mix this in with the deployment-config work you're doing?
Updated•6 years ago
|
| Reporter | ||
Comment 7•6 years ago
|
||
I'll mix this into the planned deployment-configuration-updates work
| Reporter | ||
Comment 8•6 years ago
|
||
Description
•