Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
Date: Wed, 12 Oct 2016 18:36:22 +0000 (UTC)
From: "Jing Chen (JIRA)" <jira@apache.org>
To: issues@aurora.apache.org
Message-ID: <JIRA.12901206.1443491532000.807530.1476297382186@Atlassian.JIRA>
In-Reply-To: <JIRA.12901206.1443491532000@Atlassian.JIRA>
References: <JIRA.12901206.1443491532000@Atlassian.JIRA> <JIRA.12901206.1443491532134@arcas>
Subject: [jira] [Assigned] (AURORA-1504) aurora job inspect should have a
 --write-json option
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 12 Oct 2016 18:36:24 -0000


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

Jing Chen reassigned AURORA-1504:
---------------------------------

    Assignee: Jing Chen

> aurora job inspect should have a --write-json option
> ----------------------------------------------------
>
>                 Key: AURORA-1504
>                 URL: https://issues.apache.org/jira/browse/AURORA-1504
>             Project: Aurora
>          Issue Type: Story
>          Components: Client
>            Reporter: brian wickman
>            Assignee: Jing Chen
>
> {{aurora update start}} has a {{--read-json}} option, but there's no way with the client to actually synthesize compatible json from a job_key / config pair.
> we should have {{aurora job inspect --write-json}} or possibly new {{aurora config read/write}} commands that allow users to build better automation stories around reified configurations as json blobs.
> the complications here are binding helpers that add metadata to JobConfiguration which get lost.  we might need a higher-level json schema that contains these extra fields.


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