June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1613) Merge Parsers and Completers

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1613?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-1613: ----------------------------------------- Priority: Minor (was: Major) > Merge Parsers and Completers > ---------------------------- > > Key: WFCORE-1613 > URL: https://issues.jboss.org/browse/WFCORE-1613 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Priority: Minor > > Today we have multiple parsers and completers for the same kind of syntax. It implies that any evolution done at the syntax level, needs to be duplicated in multiple places. We would have a big maintainability gain if they were merged them all together. That would also be a big effort. > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3222) CLI commands management

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3222?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3222: ---------------------------------------------- There are no plans to discover third party commands. > CLI commands management > ----------------------- > > Key: WFCORE-3222 > URL: https://issues.jboss.org/browse/WFCORE-3222 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > With the evolution of CLI to support aesh 1.0 commands, we have new use cases that CLI needs to handle. For example, to take benefit of third-party aesh commands (eg: aesh-extensions), the CLI must be able to load commands dynamically. > Currently it is difficult or impossible to achieve the following use cases: > List all commands > List enabled commands > List disabled commands > List deprecated commands > List commands that are loaded from extensions > Display errors that occurred loading commands > List commands loaded from ServiceLoader > Load commands dynamically from a jar > Load commands dynamically from a module > A dedicated command should be designed to help achieve these use cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3222) CLI commands management

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3222?page=com.atlassian.jira.plugi... ] Jean-Francois Denise closed WFCORE-3222. ---------------------------------------- Resolution: Rejected > CLI commands management > ----------------------- > > Key: WFCORE-3222 > URL: https://issues.jboss.org/browse/WFCORE-3222 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > With the evolution of CLI to support aesh 1.0 commands, we have new use cases that CLI needs to handle. For example, to take benefit of third-party aesh commands (eg: aesh-extensions), the CLI must be able to load commands dynamically. > Currently it is difficult or impossible to achieve the following use cases: > List all commands > List enabled commands > List disabled commands > List deprecated commands > List commands that are loaded from extensions > Display errors that occurred loading commands > List commands loaded from ServiceLoader > Load commands dynamically from a jar > Load commands dynamically from a module > A dedicated command should be designed to help achieve these use cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3263) add i18n to the CLI

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3263?page=com.atlassian.jira.plugi... ] Jean-Francois Denise closed WFCORE-3263. ---------------------------------------- Resolution: Rejected There are no plans to add i18n to CLI. > add i18n to the CLI > ------------------- > > Key: WFCORE-3263 > URL: https://issues.jboss.org/browse/WFCORE-3263 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Affects Versions: 3.0.1.Final > Reporter: Martin Stefanko > Assignee: Jean-Francois Denise > Priority: Optional > > Introduce i18n in the CLI subsystem. This could possibly include messages printed by the console and help description. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3450) CLI - avoid required attributes to be hard to see when using tab completion

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3450?page=com.atlassian.jira.plugi... ] Jean-Francois Denise resolved WFCORE-3450. ------------------------------------------ Resolution: Done We have colouring of required attributes. > CLI - avoid required attributes to be hard to see when using tab completion > ---------------------------------------------------------------------------- > > Key: WFCORE-3450 > URL: https://issues.jboss.org/browse/WFCORE-3450 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Miroslav Novak > Assignee: Ingo Weiss > > This is follow up for WFCORE-2283 which marked required attributes by "*" when using tab completion. Still if there are many attributes, it's hard to see all required attributes, for example in: > {code} > [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:add( > ! check-period connector-name* max-retry-interval notification-interval retry-interval-multiplier > allow-direct-connections-only cluster-connection-address* discovery-group* message-load-balancing-type producer-window-size static-connectors* > call-failover-timeout confirmation-window-size initial-connect-attempts min-large-message-size reconnect-attempts use-duplicate-detection > call-timeout connection-ttl max-hops notification-attempts retry-interval > {code} > it's not clear at the first look how many required attributes there are. > Suggestion is to group required attributes together and then provide list of other attributes, for example on the next line. Another options might be considered as well. For example to show required attributes when double pressing <tab>. > Discussed on https://developer.jboss.org/wiki/CLI-BetterCompletionForArguments?et=watc... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-153) add flake8 support for Python framework

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-153?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-153. ----------------------------------- Resolution: Done PR merged: https://github.com/Kiali-QE/kiali-qe-python/pull/45 support added via travis ci > add flake8 support for Python framework > --------------------------------------- > > Key: SWSQE-153 > URL: https://issues.jboss.org/browse/SWSQE-153 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Right now there is no util to monitor Python automation code. If we follow flake8, will be beneficial for the long run. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-278) New test case: validate user menu

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-278: ------------------------------------- Summary: New test case: validate user menu Key: SWSQE-278 URL: https://issues.jboss.org/browse/SWSQE-278 Project: Kiali QE Issue Type: QE Task Reporter: Jeeva Kandasamy Assignee: Jeeva Kandasamy Validate user menu on the navbar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-277) New test case: invalid login test

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-277: ------------------------------------- Summary: New test case: invalid login test Key: SWSQE-277 URL: https://issues.jboss.org/browse/SWSQE-277 Project: Kiali QE Issue Type: QE Task Reporter: Jeeva Kandasamy Assignee: Jeeva Kandasamy add new test case to validate invalid login -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-276) UI login code - take credentials from env.yaml

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-276?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy commented on SWSQE-276: --------------------------------------- PR sent: https://github.com/Kiali-QE/kiali-qe-python/pull/44 > UI login code - take credentials from env.yaml > ---------------------------------------------- > > Key: SWSQE-276 > URL: https://issues.jboss.org/browse/SWSQE-276 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Currently, credentials are hardcoded on UI login code. > Take credentials from env.yaml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-266) Update Istio Config page code

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-266?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-266. ----------------------------------- Resolution: Done PR merged > Update Istio Config page code > ----------------------------- > > Key: SWSQE-266 > URL: https://issues.jboss.org/browse/SWSQE-266 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Istio Config page has been modified. > Automation code needs to be updated -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2018