You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mark Chu-Carroll (JIRA)" <ji...@apache.org> on 2014/10/07 19:12:33 UTC

[jira] [Assigned] (AURORA-803) Return valid JSON structure as "job status" result with "--write-json"

     [ https://issues.apache.org/jira/browse/AURORA-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Chu-Carroll reassigned AURORA-803:
---------------------------------------

    Assignee: Mark Chu-Carroll

> Return valid JSON structure as "job status" result with "--write-json"
> ----------------------------------------------------------------------
>
>                 Key: AURORA-803
>                 URL: https://issues.apache.org/jira/browse/AURORA-803
>             Project: Aurora
>          Issue Type: Task
>          Components: Client
>            Reporter: Mark Chu-Carroll
>            Assignee: Mark Chu-Carroll
>
> Users writing scripts that use the "job status" command would prefer that when a job isn't running, that fact be expressed through a valid JSON response rather than an exit code.
> So, for example, right now, if you run "aurora job status devcluster/mchucarroll/test/foobar", you'll get back an error message on standard error with exit code 6.
> Script users would prefer a response like:
> {"job": "devcluster/mchucarroll/test/foobar", "error": "No running jobs found"}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)