{"action":"created","issue":{"url":"https://api.github.com/repos/NLeSC/compute-service-api/issues/1","repository_url":"https://api.github.com/repos/NLeSC/compute-service-api","labels_url":"https://api.github.com/repos/NLeSC/compute-service-api/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/NLeSC/compute-service-api/issues/1/comments","events_url":"https://api.github.com/repos/NLeSC/compute-service-api/issues/1/events","html_url":"https://github.com/NLeSC/compute-service-api/issues/1","id":179458922,"number":1,"title":"Cancelling a job","user":{"login":"bpmweel","id":16776108,"avatar_url":"https://avatars.githubusercontent.com/u/16776108?v=3","gravatar_id":"","url":"https://api.github.com/users/bpmweel","html_url":"https://github.com/bpmweel","followers_url":"https://api.github.com/users/bpmweel/followers","following_url":"https://api.github.com/users/bpmweel/following{/other_user}","gists_url":"https://api.github.com/users/bpmweel/gists{/gist_id}","starred_url":"https://api.github.com/users/bpmweel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bpmweel/subscriptions","organizations_url":"https://api.github.com/users/bpmweel/orgs","repos_url":"https://api.github.com/users/bpmweel/repos","events_url":"https://api.github.com/users/bpmweel/events{/privacy}","received_events_url":"https://api.github.com/users/bpmweel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-27T10:47:05Z","updated_at":"2016-09-28T10:12:48Z","closed_at":null,"body":"We discussed what the best way was to cancel a job. I found [this stackoverflow question](http://stackoverflow.com/questions/17529315/hateoas-how-to-model-link-relations-that-change-state) which provides a number of solutions.\r\n\r\nIt mentions a new verb for http called PATCH which may be a fit, what do you guys think?"},"comment":{"url":"https://api.github.com/repos/NLeSC/compute-service-api/issues/comments/250127140","html_url":"https://github.com/NLeSC/compute-service-api/issues/1#issuecomment-250127140","issue_url":"https://api.github.com/repos/NLeSC/compute-service-api/issues/1","id":250127140,"user":{"login":"LourensVeen","id":17028817,"avatar_url":"https://avatars.githubusercontent.com/u/17028817?v=3","gravatar_id":"","url":"https://api.github.com/users/LourensVeen","html_url":"https://github.com/LourensVeen","followers_url":"https://api.github.com/users/LourensVeen/followers","following_url":"https://api.github.com/users/LourensVeen/following{/other_user}","gists_url":"https://api.github.com/users/LourensVeen/gists{/gist_id}","starred_url":"https://api.github.com/users/LourensVeen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LourensVeen/subscriptions","organizations_url":"https://api.github.com/users/LourensVeen/orgs","repos_url":"https://api.github.com/users/LourensVeen/repos","events_url":"https://api.github.com/users/LourensVeen/events{/privacy}","received_events_url":"https://api.github.com/users/LourensVeen/received_events","type":"User","site_admin":false},"created_at":"2016-09-28T10:12:48Z","updated_at":"2016-09-28T10:12:48Z","body":"I like cayuu's solution in that thread better than my original idea of reifying the runner and then deleting it: make the status a subresource that you can then PUT to. It's closer to intuitive for most people I think.\r\n\r\nPATCH would be an alternative for that where the status is part of the job, but then the question arises what else you can patch, and it's not as well known I think (but maybe that's just because I'd never heard of it :-)). Also maybe canceling the job would cause other parts of it to change, so that you end up with a current state, a patch, and a new state which isn't simply the current state plus the changes in the patch."}}
{"actor":{"display_login":"LourensVeen"}}