[
https://issues.apache.org/jira/browse/AURORA-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979742#comment-14979742
]
Maxim Khutornenko commented on AURORA-1492:
-------------------------------------------
+1.
You may want to take a look at the newly added getJobUpdateDiff API for the
idea:
https://github.com/apache/aurora/blob/888f9a3ccf8ee84dbf30f9bb612469ac70c019f7/src/main/java/org/apache/aurora/scheduler/thrift/ReadOnlySchedulerImpl.java#L359
As for the client output, perhaps aligning it with the 'aurora job diff' output
(minus the diff part):
https://github.com/apache/aurora/blob/5609fc2307892584fbcf6fb66ff134cb3cb6dcf0/src/main/python/apache/aurora/client/cli/jobs.py#L293-L297
> Improve "aurora update start" command output
> --------------------------------------------
>
> Key: AURORA-1492
> URL: https://issues.apache.org/jira/browse/AURORA-1492
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Sisir Koppaka
> Priority: Minor
> Labels: newbie
>
> Customer feedback when trying to update a single job instance:
> {quote}
> It would provide peace of mind if somewhere in the output of {{aurora update
> start}} it said "1 of X instances of <job_key> will be updated" just so that
> I knew that I didn't mess up the command.
> {quote}
> The diff details are already available in the {{startJobUpdate}} rpc, so
> reporting the above should be trivial.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
