[jira] [Resolved] (AURORA-168) allow aurora client commands to operate over multiple jobs

["Bill Farner (JIRA)" <ji...@apache.org>]

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

Bill Farner resolved AURORA-168.
--------------------------------
    Resolution: Won't Fix

> allow aurora client commands to operate over multiple jobs
> ----------------------------------------------------------
>
>                 Key: AURORA-168
>                 URL: https://issues.apache.org/jira/browse/AURORA-168
>             Project: Aurora
>          Issue Type: Task
>          Components: Client
>            Reporter: brian wickman
>            Priority: Minor
>
> The idea would be to somehow allow chaining of client commands together, e.g.
> {noformat}
> aurora create/update job1 job2 job3 job4 my_config.aurora
> aurora kill job1 job2 job3 job4
> {noformat}
> By default it runs them in order (stops if any of them fails.)
> Maybe add a --parallel option that runs them in parallel instead.
> This would be useful for some roles which have many almost-identical jobs within the same file.  A common pattern is to roll out a new package and run updates for all jobs in parallel.



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