|Subject:||Re: Command output guidelines for asadmin subcommands|
|From:||Tom Mueller (tom....@oracle.com)|
|Date:||Sep 21, 2010 5:58:59 pm|
Yes, except for list-backups. Tom
On Sep 21, 2010, at 5:02 PM, Rebecca Parks <rebe...@oracle.com> wrote:
Has this change been implemented?
On 09/16/10 09:05, Tom Mueller wrote:
Any objections if I make the change from --verbose to --long for all of the list
commands that currently support --verbose at once? Please let me know if you
don't want me to do this to your command. The current list is: list-application-refs list-applications list-backups list-components list-connector-security-maps list-instances list-nodes-config list-nodes-ssh list-nodes list-resource-adapter-configs For list-connector-security-maps and list-resource-adapter-configs, verbose will
still be an alias for long since this option was there in 3.0. Tom On 9/15/2010 2:56 PM, Tom Mueller wrote:
Asadmin Command owners:
Today, ASArch reviewed the asadmin command output guidelines as documented here:
and approved them.
Command owners, please review the output of your commands relative to these
guidelines and make changes where necessary. Some issues have been filed
already for certain commands and as part of completing the work for issue 12236,
I'll be scanning through the output of other commands and either fixing them or
filing additional issues.
Note that much of the first section is optional for 3.1 - the only required part
is to rename --verbose to --long for the various list commands. The long term
implementation intent for columnar output from list commands is to provide a way
that the command can just return the data items and column headings in a data
structure to asadmin, and then asadmin can do the formatting. This way, the same
output can be used by both the REST interface and asadmin.
As we gain experience with these guidelines, I'm sure that some enhancements and
modifications will be needed, so please keep that in mind.
Please let me know if you have any questions/concerns.