[jboss-jira] [JBoss JIRA] (WFCORE-1939) Tabulator in CLI could suggest actual values for attributes for operations

[Jean-Francois Denise (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13345878#comment-13345878 ] 

Jean-Francois Denise commented on WFCORE-1939:
----------------------------------------------

That would be perfect. Yes, that is not urgent at all.
JF

> Tabulator in CLI could suggest actual values for attributes for operations
> --------------------------------------------------------------------------
>
>                 Key: WFCORE-1939
>                 URL: https://issues.jboss.org/browse/WFCORE-1939
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: CLI, Domain Management
>            Reporter: Miroslav Novak
>              Labels: user_experience
>
> There are number of cases where is necessary to execute CLI operation to actually get value for attribute to another CLI operation. For example I want to list all messages for subscription on the topic then it's necessary to get names of all subscriptions by:
> {code}
> [standalone at 172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-all-subscriptions
> {
>     "outcome" => "success",
>     "result" => [
>         {
>             "durable" => true,
>             "queueName" => "172\\.16\\.10\\.15_VM1_SPAgent55_0.SP_CallForOffersEH_55_EHID_1PF4",
>             "clientID" => "172.16.10.15_VM1_SPAgent55_0",
>             "messageCount" => 0,
>             "deliveringCount" => 0,
>             "name" => "SP_CallForOffersEH_55_EHID_1PF4",
>             "consumers" => [{
>                 "creationTime" => 1478261489444L,
>                 "consumerID" => 4,
>                 "browseOnly" => false,
>                 "connectionID" => "-1638816479",
>                 "sessionID" => "d1149360-a287-11e6-bb34-97e27f67b29e"
>             }]
>         },
>         {
>             "durable" => true,
>             "queueName" => "172\\.16\\.10\\.18_VM1_SPAgent23_0.SP_CallForOffersEH_23_EHID_1PF0",
>             "clientID" => "172.16.10.18_VM1_SPAgent23_0",
>             "messageCount" => 0,
>             "deliveringCount" => 0,
>             "name" => "SP_CallForOffersEH_23_EHID_1PF0",
>             "consumers" => [{
>                 "creationTime" => 1478261516648L,
>                 "consumerID" => 0,
>                 "browseOnly" => false,
>                 "connectionID" => "-1794279882",
>                 "sessionID" => "e14e5343-a287-11e6-9311-4d8e66b2ef14"
>             }]
>         }
>     ]
> }
> {code}
>  
> so name of subscription  {{SP_CallForOffersEH_55_EHID_1PF4}} could be used in: {code}
> [standalone at 172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=SP_CallForOffersEH_55_EHID_1PF4){code}
> The improvement would allow to just press tab in: {code}
> [standalone at 172.16.10.17:9990 /] /subsystem=messaging-activemq/server=default/jms-topic=HQ_ProductFamilyT23:list-messages-for-subscription(queue-name=...  <-- tab here would suggest which queues are available {code}
> and it would suggest queue names of available subscriptions.
> There are more places like this - for example :
> {code}
> /subsystem=messaging-activemq/server=default:rollback-prepared-transaction(transaction-as-base-64=... <-- tab here
> {code}
> would provide available prepared transactions which can be commit.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)