Many months ago we introduced dedicated settings variables for lib, repo and client rather then stuffing everything into a single variable.
The single variable we used to have was: wgWBSettings
Right now we have
- wgWBSettings: for lib settings
- wgWBRepoSettings: for repo settings
- wgWBClientSettings: fir client settings
Currently they are all merged together for all code accessing settings, so that old configuration that stuffs everything into wgWBSettings will still work.
Right now there are two changes on gerrit that prevent loading of client settings on repo and repo settings on client.
These will break any configuration that puts configuration needed by repo in the client variable or the other way around. Such configuration was possible before there commits though not before the change from one to 3 config variables and has never been intended to be supported. Presumably no setup is using such bad config, so these commits should not cause problems.
However continuing the cleanup of the configuration system requires dropping support of the all settings in one variable configuration at some point. This means the configuration on the WMF cluster should be updated (as it apparently still is stuffing everything in wgWBSettings) and that this configuration should first be tested.
Until that happens development is blocked by ops tasks.
Version: master
Severity: normal