Flow runs, jobs and logs in the API; checks by heads issue #26
closed: completed andymccall opened this · 0 comments
andymccall
From metalgear's feedback:
Item 11: watching a run meant scraping the Flow pages. There is no API for runs, jobs or logs, and checks/{state} needs the state hash while a client has head hashes.
Item 13: unknown /api/v1 routes answer with the HTML 404 page.
Add read endpoints for runs, a run's jobs and a job's log. Make checks accept heads or a bookmark, and answer unknown API routes with a JSON problem.
From metalgear's feedback:
checks/{state}needs the state hash while a client has head hashes./api/v1routes answer with the HTML 404 page.Add read endpoints for runs, a run's jobs and a job's log. Make checks accept heads or a bookmark, and answer unknown API routes with a JSON problem.