[ https://issues.apache.org/jira/browse/AURORA-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Staffin updated AURORA-1577: ------------------------------------- Affects Version/s: 0.11.0 > aurora cli requires jobkey with --read-json, but ignores it > ----------------------------------------------------------- > > Key: AURORA-1577 > URL: https://issues.apache.org/jira/browse/AURORA-1577 > Project: Aurora > Issue Type: Bug > Components: Client > Affects Versions: 0.11.0, 0.10.0 > Reporter: Benjamin Staffin > Priority: Minor > > Various {{aurora job}} subcommands have {{--read-json}} available for loading > a single job definition from a JSON document. When used in this mode, the > commands still require a jobkey to be given as a parameter, but that jobkey > is ignored in favor of the jobkey contained in the json data. > e.g. if you have a json file that describes a job {{a/a/a/a}}, the following > commands produce identical results - both will create job {{a/a/a/a}}: > {code} > aurora job create a/a/a/a --read-json foo.json > aurora job create z/z/z/z --read-json foo.json > {code} > and the following fails with an error message: > {code} > aurora job create --read-json foo.json > {code} > Since the json format already contains a jobkey spec, it would make sense to > omit the jobkey parameter from the commandline when using {{--read-json}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)