Page MenuHomePhabricator

Re-run config validation from `bin/search`
ClosedPublic

Authored by epriestley on Mar 28 2017, 8:54 PM.
Tags
None
Referenced Files
F19035733: D17574.id.diff
Nov 25 2025, 5:59 PM
F19028222: D17574.diff
Nov 24 2025, 3:16 PM
F18869913: D17574.id.diff
Nov 4 2025, 2:17 PM
F18836752: D17574.diff
Oct 27 2025, 3:29 AM
F18820943: D17574.id.diff
Oct 22 2025, 6:07 PM
F18817706: D17574.diff
Oct 21 2025, 5:42 PM
F18673239: D17574.id42278.diff
Sep 25 2025, 9:50 AM
F18566130: D17574.id.diff
Sep 9 2025, 2:20 PM
Subscribers
None

Details

Summary

Ref T12450. Normally, we validate config when:

  • You restart the webserver.
  • You edit it with bin/config set ....
  • You edit it with the web UI.

However, you can also change config by editing local.json, some_env.conf.php, a SiteConfig class, etc. In these cases, you may miss config warnings.

Explicitly re-run search config checks from bin/search, similar to the additional database checks we run from bin/storage, to try to produce a better error message if the user has made a configuration error.

Test Plan
$ ./bin/search init
Usage Exception: Setting "cluster.search" is misconfigured: Invalid search engine type: elastic. Valid types are: elasticsearch, mysql.

Diff Detail

Repository
rP Phabricator
Branch
search4
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 16203
Build 21515: Run Core Tests
Build 21514: arc lint + arc unit

Event Timeline

This revision is now accepted and ready to land.Mar 28 2017, 9:46 PM
This revision was automatically updated to reflect the committed changes.