Skip to content

Scheduler API server

The current way of using the scheduler is instantiating the Scheduler class, which only has a local implementation, which itself hits the database directly.

It would make sense to provide a backend API server to centralize database connections and logging, all the more so when we will be adding more listers to the infrastructure soon.


Migrated from T725 (view on Phabricator)