Add CLI or API to produce overview of scheduled jobs

[barry-luijten]

I am using deck-chores on a Docker Swarm cluster and I'm combining it with a self-hosted HealthChecks instance and Runitor to track the results of my scheduled jobs. That works very well, but I'm missing a way of checking if jobs are being scheduled by deck-chores after I deploy a new service and which jobs are currently being managed by deck-chores. I'm now checking the output on the console of each deck-chores container, but that is not the easiest way to do it.
It would be nice if it was possible to run a command in a deck-chores container that produces a list of currently scheduled jobs. The output can be tabular/greppable or JSON, showing all details of the jobs, including the schedule, the container, the command etc.
A script that calls this command and forwards the output to a central location (e.g. HealthChecks, webhook or a database), can then be scheduled as a deck-chores task for each of the deck-chores containers (I'm already using this to check if all of my dc-containers are still running).
This feature would allow anyone to build their own "deck-chores UI" and it's a lot easier to implement then a full-fledged API or web-gui.

[funkyfuture]

thanks for your feedback.

in issue #76 there are already some thoughts regarding the required refactoring for an extended CLI, including means of inter-process communication.

in #95 i mention a plugin system that could provide various log outputs. maybe that could also be used for custom subcommands, which reg. your ideas might be usable to spin up a web ui.

please mind that someone will have to implement all this, and i personally don't plan on doing this directly (aside support, review and bearing the burden of long-term maintenance).