[jira] [Commented] (AURORA-1504) aurora job inspect should have a --write-json option
[
https://issues.apache.org/jira/browse/AURORA-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15603911#comment-15603911
]
Jing Chen commented on AURORA-1504:
---
The changes will prevent the command from rendering {color:blue}contact{color}
if no contact is given both in json and non-json format, which returns
{color:red}{color} before.
> 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)
[jira] [Commented] (AURORA-1504) aurora job inspect should have a --write-json option
[
https://issues.apache.org/jira/browse/AURORA-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15598759#comment-15598759
]
Jing Chen commented on AURORA-1504:
---
introduce option {color:blue}--write-json{color} for {color:blue}aurora job
inspect{color}
> 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)
[jira] [Commented] (AURORA-1504) aurora job inspect should have a --write-json option
[
https://issues.apache.org/jira/browse/AURORA-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107958#comment-15107958
]
Benjamin Staffin commented on AURORA-1504:
--
If there were such a higher-level json schema, it would make sense for that to
have a list of jobs, just like the pystachio schema, rather than only one job
object. That would dovetail nicely with AURORA-1577 as well.
> 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
>
> {{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)
