New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 824479 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
no...@chromium.org
mar...@chromium.org
qyears...@chromium.org
█ emso@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Cache/store configs to avoid disruptions in case luci-config issues

Project Member Reported by qyears...@chromium.org, Mar 21 2018 
For some time yesterday and today, luci-config didn't return any service configs for tricium ( bug 824386 ).

It may be a good idea to store configs with the tricium-service in case of errors fetching configs in the future, to make the tricium service a little more resilient.

Comment 1 by no...@chromium.org, Mar 21 2018 

I don’t known how much valueable is this. If luci-config looses all configs, tricium not working would be the least of problems. 

Note that fetch was successful. This workaround wouldn’t work for project config sets that come and go: absence of a config isn’t an error

Comment 2 by qyears...@chromium.org, Mar 21 2018

Status: WontFix (was: Available)
I suppose that makes sense.

I was filing this mainly because I was wondering if it's a good practice for services in general.

Closing for now.
►

Sign in to add a comment