Byron Nevins wrote on 06/29/09 11:00:
> To start using the new CLI just set this environmental variable
> semi-permanently
>
> ASADMIN_NEW=true
The above enables support for asadmin options both intermixed with
and separate from command options.
For example, you can use either:
$ asadmin list-applications --host foo --port 5656
or
$ asadmin --host foo --port 5656 list-applications
If you use the latter form, *all* the asadmin "meta-options" need
to come before the command-specific options.
As soon as I get some review of the changes, I'm going to commit a
version with more extensive updates. The asadmin client will know
about the names and types of the parameters supported by a remote
command (it gets this information by asking the server). This
new capability will still need to be enabled as described above.
I'm hoping to get some real feedback on this new version before
I switch it to be the default. This shouldn't feel any different
than the above to the casual user; mostly it just removes a bunch
of special case code in the asadmin client, allowing it to handle
new remote commands in a more extensible fashion.