[AURORA-1168] beta-update list should use a hierarchy for query specifications

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8.0
• Component/s: Client
• Sprint: Twitter Aurora Q1'15 Sprint 5
• Story Points: 3
• Assignee: Bill Farner
• Reporter: Bill Farner
• Created: 04/Mar/15 01:07
• Updated: 04/May/15 13:12
• Resolved: 20/Mar/15 00:45

Description

$ 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

This means that to query for updates for a specific, job, one must use a command like this:

$ aurora beta-update list --job devcluster/vagrant/test/http_example devcluster

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:

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

Issue Links

• blocks: AURORA-904 0.8.0 Release Candidate