Luigi: Task history should have an HTTP API

[stephenpascoe]

At the moment there is no json response for the task_history HTTP routes so it's difficult to write clients that consume the task_history. I'm currently talking directly to the DB which IMO is cheating.

I suggest either adding public task_history methods to the scheduler classes or adapting the tornado handlers to return json when asked.

I should have time to do an implementation in the near future so please discuss here.

[jwg4]

This would be great, I am parsing the HTML to find out whether the task most recently succeeded or not.

[erikbern]

would love it if someone can give the task history a bit more love!

[LeeKamentsky]

I'm looking for this as well. For my use case, REST calls to get the rows from the task_events, task_parameters and tasks tables by task_id would do it. I'd be willing to contribute a PR if you need it. Not sure on the outset how to write tests against the API...

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If closed, you may revisit when your time allows and reopen! Thank you for your contributions.