maas-cli argument handling inconsistencies

[Daniel Westervelt]

with some maas-cli cmdlines it seems key:value (name=value) pairs are required to be stated explicitly while others just require value. For instance consider the following two cmdlines:

FAILS: (with value only)
maas-cli admin nodes accept node-5bf10db6-5f24-11e2-90e2-8c705ac92df0
'node-5bf10db6-5f24-11e2-90e2-8c705ac92df0' is not a name=value pair

WORKS: (with name=value)
maas-cli admin nodes accept system_id=node-5bf10db6-5f24-11e2-90e2-8c705ac92df0

While node actions only require (value) to work - see below:

maas-cli admin node release node-5bf10db6-5f24-11e2-90e2-8c705ac92df0
maas-cli admin node stop node-5bf10db6-5f24-11e2-90e2-8c705ac92df0
etc...

[Gavin Panella (allenap)]

It's not so much inconsistent:

> maas-cli admin nodes accept system_id=node-5bf10db6-5f24-11e2-90e2-8c705ac92df0

Here the `accept` call is being sent to the `nodes` handler, passing the
`system_id` argument.

> maas-cli admin node release node-5bf10db6-5f24-11e2-90e2-8c705ac92df0

Here the `release` call is being sent to the node identified as
`node-5bf10db6-5f24-11e2-90e2-8c705ac92df0`.

What it is, is unintuitive, especially the second one; I'd expect
`release` to be last:

  maas-cli admin node node-5bf10db6-5f24-11e2-90e2-8c705ac92df0 release

[Jerzy Husakowski (jhusakowski)]

The behavior is as expected. Moreover, maas-cli is no longer supported.