Bill Farner created AURORA-1168:
-----------------------------------
Summary: beta-update list should use a hierarchy for query
specifications
Key: AURORA-1168
URL: https://issues.apache.org/jira/browse/AURORA-1168
Project: Aurora
Issue Type: Task
Components: Client
Reporter: Bill Farner
{noformat}
$ aurora beta-update list -h
usage: aurora beta-update list [-h] [--job CLUSTER/ROLE/ENV/NAME]
[--role ROLENAME] [--user username]
[--status
{ROLLED_BACK,ROLL_FORWARD_PAUSED,ROLL_FORWARD_AWAITING_PULSE,ERROR,ROLLING_BACK,ROLLING_FORWARD,ROLLED_FORWARD,ROLL_BACK_PAUSED,FAILED,ABORTED,ROLL_BACK_AWAITING_PULSE}]
[--write-json] [--verbose]
[--skip-hooks hook,hook,...]
clustername
{noformat}
This means that to query for updates for a specific, job, one must use a
command like this:
{noformat}
$ aurora beta-update list --job devcluster/vagrant/test/http_example devcluster
{noformat}
In addition to being redundant, this is less user-friendly than the
hierarchical syntax we use in other places.
I suggest we change the client to drop the job and role options, and instead
support commands like:
{noformat}
aurora beta-update list cluster
aurora beta-update list cluster/role
aurora beta-update list cluster/role/env
aurora beta-update list cluster/role/env/job
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
