You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Joe Smith (JIRA)" <ji...@apache.org> on 2015/05/12 02:55:59 UTC
[jira] [Updated] (AURORA-1316) Consolidate last_modified in client
update output
[ https://issues.apache.org/jira/browse/AURORA-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Smith updated AURORA-1316:
------------------------------
Summary: Consolidate last_modified in client update output (was: Consolidate lastModified in client update output)
> Consolidate last_modified in client update output
> -------------------------------------------------
>
> Key: AURORA-1316
> URL: https://issues.apache.org/jira/browse/AURORA-1316
> Project: Aurora
> Issue Type: Bug
> Components: Client, Usability
> Reporter: Joe Smith
> Assignee: Joe Smith
>
> If they run an {{update info}} they'll see:
> {noformat}
> $ aurora update info us-west/myservice/environment/job_name 9001-dh1bab-unique-update-id --write-json
> {
> <snip>
> "last_updated": 1431056513956,
> <snip>
> {noformat}
> However, if they do {{update list}}:
> {noformat}
> $ aurora update list us-west/myservice/environment/job_name --write-json
> "lastModified": "2015-05-08T19:01:03",
> <snip>
> {noformat}
> My intuition is we should consolidate to use lastModified with the same formatted timestamp, as that will be both human- and machine-readable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)