[JBoss JIRA] (WFCORE-284) Rewrite CLI FileArgumentTestCase
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-284?page=com.atlassian.jira.plugin... ]
Jean-Francois Denise closed WFCORE-284.
---------------------------------------
Resolution: Cannot Reproduce Bug
These tests are woking fine in wildfly-core upstream.
> Rewrite CLI FileArgumentTestCase
> --------------------------------
>
> Key: WFCORE-284
> URL: https://issues.jboss.org/browse/WFCORE-284
> Project: WildFly Core
> Issue Type: Task
> Components: CLI
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
>
> The test has been failing sporadically for awhile. One of the problems is to figure out the conditions under which the test fails. They haven't been determined so far. Perhaps, attempts to simplify and clean up the logic in the test will help.
> The test is org.jboss.as.test.integration.management.cli.FileArgumentTestCase
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-1939) Tabulator in CLI could suggest actual values for attributes for operations
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1939?page=com.atlassian.jira.plugi... ]
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@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@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@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)
9 years, 3 months
[JBoss JIRA] (WFCORE-1939) Tabulator in CLI could suggest actual values for attributes for operations
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1939?page=com.atlassian.jira.plugi... ]
Miroslav Novak commented on WFCORE-1939:
----------------------------------------
[~jdenise] I'll create some google doc and link it here. It will be easier for tracking. I have some more priority work atm so not sure now when I get to it. Hopefully this month.
> 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@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@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@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)
9 years, 3 months
[JBoss JIRA] (WFCORE-1939) Tabulator in CLI could suggest actual values for attributes for operations
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1939?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-1939:
----------------------------------------------
Hi [~mnovak],
that would be very helpful to start with your expertise. Possibly other people involved in UX testing could complete your list. At some point I should ask elytron for their requirements.
Thanks again for helping!
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@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@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@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)
9 years, 3 months
[JBoss JIRA] (WFCORE-1939) Tabulator in CLI could suggest actual values for attributes for operations
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1939?page=com.atlassian.jira.plugi... ]
Miroslav Novak commented on WFCORE-1939:
----------------------------------------
[~jdenise] I do not have overall knowledge of all subsystems. I'm focused on messaging which has big model and I could start to create such list for it. To provide complete list for all subsystem will require participation of experts from each subsystem.
> 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@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@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@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)
9 years, 3 months
[JBoss JIRA] (WFLY-7865) We cannot define CS file location outside of EAP directory
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7865?page=com.atlassian.jira.plugin.... ]
Hynek Švábek commented on WFLY-7865:
------------------------------------
No, there is not path resource named java.io.tmpdir. It was only example. I don't think it is possible to get this functionality through relative-to. What do you think?
It doesn't matter how but I expect some way to define path to CS file outside of EAP folder.
> We cannot define CS file location outside of EAP directory
> ----------------------------------------------------------
>
> Key: WFLY-7865
> URL: https://issues.jboss.org/browse/WFLY-7865
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
> Priority: Critical
>
> We aren't able define location of CS file outside of EAP directory. When user has CS file on NFS he isn't able to reach this file.
> Define CS file location to JBOSS_HOME/Standalone/data directory:
> {code}
> /subsystem=elytron/credential-store=CredStore001:add(uri="cr-store://test/cs123.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=jboss.server.data.dir)
> {code}
> When I try set relative to TEMP directory:
> {code}
> /subsystem=elytron/credential-store=CredStore002:add(uri="cr-store://test/cs123.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=java.io.tmpdir)
> {code}
> I get this error
> {code}
> {
> "outcome" => "failed",
> "failure-description" => {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"java.io.tmpdir\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore002 is missing [jboss.server.path.\"java.io.tmpdir\"]"]
> },
> "rolled-back" => true
> }
> {code}
> *NOTE:*
> *relative-to* is resolved here https://github.com/wildfly-security/elytron-subsystem/blob/c223be428b9a6f...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months