April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3864) Kubernetes configuration for the remote debug

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3864?page=com.atlassian.jira.plugi... ] Massimiliano Dessi commented on DROOLS-3864: -------------------------------------------- https://github.com/desmax74/openshift-hacep/commit/ca7f465cf2084209d8814a... > Kubernetes configuration for the remote debug > --------------------------------------------- > > Key: DROOLS-3864 > URL: https://issues.jboss.org/browse/DROOLS-3864 > Project: Drools > Issue Type: Feature Request > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3864) Kubernetes configuration for the remote debug

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-3864: ------------------------------------------ Summary: Kubernetes configuration for the remote debug Key: DROOLS-3864 URL: https://issues.jboss.org/browse/DROOLS-3864 Project: Drools Issue Type: Feature Request Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4407) Cannot configure Elytron security domain using embedded server in admin mode

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4407: ------------------------------------ Summary: Cannot configure Elytron security domain using embedded server in admin mode Key: WFCORE-4407 URL: https://issues.jboss.org/browse/WFCORE-4407 Project: WildFly Core Issue Type: Bug Components: Embedded Environment: Reporter: Yeray Borges Assignee: Yeray Borges There are some configurations that are impossible to do using the embedded server, for example, we cannot create a security domain in Elytron that references a security domain in the security subsystem: {noformat} embed-server --server-config=standalone-full-ha.xml --std-out=echo /subsystem=security/security-domain=my-sec-domain:add(cache-type=default) /subsystem=security/security-domain=my-sec-domain/authentication=classic:add(login-modules=[{code=RealmUsersRoles, flag=required, module=RealmUsersRoles, module-options=[("usersProperties"=>"usersProperties"),("rolesProperties"=>"rolesProperties")]}]) /subsystem=security/elytron-realm=my-sec-domain:add(legacy-jaas-config=my-sec-domain) /subsystem=elytron/security-domain=my-sec-domain:add(realms=[{realm=my-sec-domain}],default-realm=my-sec-domain,permission-mapper=default-permission-mapper) stop-embedded-server {noformat} The execution of these operations in an embedded server running in admin-mode throws the following error: {noformat} [standalone@embedded /] /subsystem=elytron/security-domain=my-sec-domain:add(realms=[{realm=my-sec-domain}],default-realm=my-sec-domain,permission-mapper=default-permission-mapper) 12:30:53,429 ERROR [org.jboss.as.controller.management-operation] (pool-3-thread-1) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("security-domain" => "my-sec-domain") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.my-sec-domain"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.my-sec-domain.initial is missing [org.wildfly.security.security-realm.my-sec-domain]"] } { "outcome" => "failed", "failure-description" => { "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.my-sec-domain"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.my-sec-domain.initial is missing [org.wildfly.security.security-realm.my-sec-domain]"] }, "rolled-back" => true } {noformat} The problem here is Elytron security domain services cannot be up because they require the legacy installed realm services, which are not up when we are using embedded in admin-only mode. The SecurityDomain advertises no runtime operation, if no services are installed that would ever depend on security domain we may be able to skip installing some of these services entirely and allow their configuration in embedded / admin-only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3784: ------------------------------------- [~dmarrazzo] Hi, on weekly meeting, we discussed the save principles also for constraints component [1] and we think our decision should be same for data types so for constraints, could you provide your feedback also for the constrains component? Thank you! [1] !constraints.png|thumbnail! > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, constraints.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3784: -------------------------------- Attachment: constraints.png > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, constraints.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3784: -------------------------------- Attachment: (was: Screenshot from 2019-04-08 17-46-26.png) > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, constraints.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3784) Increase the advanced user productivity when he creates a new Data Type

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3784?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3784: -------------------------------- Attachment: Screenshot from 2019-04-08 17-46-26.png > Increase the advanced user productivity when he creates a new Data Type > ----------------------------------------------------------------------- > > Key: DROOLS-3784 > URL: https://issues.jboss.org/browse/DROOLS-3784 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Donato Marrazzo > Assignee: Elizabeth Clayton > Priority: Minor > Labels: Field, UX, UXTeam, drools-tools > Attachments: DT_List1.png, DT_List1b.png, Screenshot from 2019-03-25 15-27-51.png, constraints.png, nested.png, type-selector.png > > > The Data Type editor could be improved in terms of productivity and usability. > Ideally, the user should be able to create a complex type minimizing the mouse usage. > 1) Saving the node is an overhead for basic data type (e.g. age: number) > 2) Some actions in the kebab menu should be more visible and available even before saving the type (as standalone icon / buttons). Especially, insert nested, delete. > 3) Select type in the selector by typing the name of the type (see screenshot): it already works but it consider just the first letter typed. Since, by convention, all custom types starts with `t` letter, it would be better consider at least 2 letters. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-665) Test case coverage for Istio

by Michael Foley (Jira)

[ https://issues.jboss.org/browse/SWSQE-665?page=com.atlassian.jira.plugin.... ] Michael Foley edited comment on SWSQE-665 at 4/8/19 10:34 AM: -------------------------------------------------------------- [~yuaxu] can you update this and complete as part of TP10? Work with [~pyadav] and [~skondkar] Thank you. was (Author: mfoley): [~yuaxu] can you update this and complete as part of TP10? Thank you. > Test case coverage for Istio > ---------------------------- > > Key: SWSQE-665 > URL: https://issues.jboss.org/browse/SWSQE-665 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > Some areas are missing which we are not testing for Istio. Need to focus on that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-668) Checklist for custom fields in order to support existing and future workflows for Istio

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-668?page=com.atlassian.jira.plugin.... ] Prachi Yadav reassigned SWSQE-668: ---------------------------------- Assignee: Yuanlin Xu > Checklist for custom fields in order to support existing and future workflows for Istio > --------------------------------------------------------------------------------------- > > Key: SWSQE-668 > URL: https://issues.jboss.org/browse/SWSQE-668 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-665) Test case coverage for Istio

by Michael Foley (Jira)

[ https://issues.jboss.org/browse/SWSQE-665?page=com.atlassian.jira.plugin.... ] Michael Foley commented on SWSQE-665: ------------------------------------- [~yuaxu] can you update this and complete as part of TP10? Thank you. > Test case coverage for Istio > ---------------------------- > > Key: SWSQE-665 > URL: https://issues.jboss.org/browse/SWSQE-665 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > Some areas are missing which we are not testing for Istio. Need to focus on that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019