Right now, we are using both config.yaml and localsettings.js to configure Parsoid. The former is used by service-runner, and the latter is used by Parsoid. Once we resolve T141370, we should be able to use config.yaml for configuring the production Parsoid setup.
On the other hand, with localsettings.js, we control updates and deploys in Parsoid land without needing to go through Puppet and ops review and merge. So, that needs to be factored in as well.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Arlolra | T141371 Use service-runner's config.yaml for all Parsoid configuration instead of relying on localsettings.js | |||
| Resolved | Arlolra | T141370 Use the same logger to log service-runner events and Parsoid events |
We've moved to using service-runner's logger and metrics reporter, which are now handled in puppet controlled config.yaml. That makes a nice divide between service-runner and Parsoid configs, which we'd like to retain the deploy repo.