Minor Description
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:
aurora job create a/a/a/a --read-json foo.json aurora job create z/z/z/z --read-json foo.json
and the following fails with an error message:
aurora job create --read-json foo.json
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.