You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kie.apache.org by "RichardW98 (via GitHub)" <gi...@apache.org> on 2024/03/08 20:56:51 UTC
[PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
RichardW98 opened a new pull request, #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570
doc for knative eventing in operator
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "ricardozanini (via GitHub)" <gi...@apache.org>.
ricardozanini commented on PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#issuecomment-1989124897
@kaldesai can you ptal?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "ricardozanini (via GitHub)" <gi...@apache.org>.
ricardozanini commented on PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#issuecomment-1991522878
@wmedvede can you take a look?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "ricardozanini (via GitHub)" <gi...@apache.org>.
ricardozanini commented on code in PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#discussion_r1520142970
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a KnativeEventing CR.
+2. a broker named `default` is created. Currently all Triggers created by Sonataflow operator will read events from `default`
+
+== Configuring the workflow
+
+In order for operator to create the `SinkBinding` resources, the workflow must provide the sink information in `spec.sink`.
+
+.Example of a workflow with events
+[source,yaml]
Review Comment:
```suggestion
[source,yaml,subs="attributes+"]
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "domhanak (via GitHub)" <gi...@apache.org>.
domhanak commented on code in PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#discussion_r1519403026
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+=== Prerequisite
Review Comment:
To fix the build
```suggestion
== Prerequisite
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "kaldesai (via GitHub)" <gi...@apache.org>.
kaldesai commented on code in PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#discussion_r1520870756
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+{operator_name} can analyze the event definitions from the `spec.flow` and create `SinkBinding`/`Trigger` based on the type of the event. Then the workflow service can utilize them for event communications. The same purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here].
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a `KnativeEventing` CR.
+2. a broker named `default` is created. Currently all Triggers created by the {operator_name} will read events from `default`
+
+== Configuring the workflow
+
+For the operator to create the `SinkBinding` resources, the workflow must provide the sink information in `spec.sink`.
+
+.Example of a workflow with events
+[source,yaml,subs="attributes+"]
+--
+apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlow
+metadata:
+...
+spec:
+ sink:
+ ref: <1>
+ name: default
+ namespace: greeting
+ apiVersion: eventing.knative.dev/v1
+ kind: Broker
+ flow:
+ events: <2>
+ - name: requestQuote
+ type: kogito.sw.request.quote
+ kind: produced
+ - name: aggregatedQuotesResponse,
+ type: kogito.loanbroker.aggregated.quotes.response,
+ kind: consumed,
+ source: /kogito/serverless/loanbroker/aggregator
+...
+--
+<1> `spec.sink.ref` defines the sink that all created sinkBinding will use as the destination sink for producing events
+<2> `spec.flow.events` lists all the events referenced in the workflow. Events with `produced` kind will trigger the creation of `SinkBindings` by the {operator_name}, while those labeled as `consumed` will lead to the generation of `Triggers`.
+
+[NOTE]
+====
+Knative resources is not watched by the operator, indicating that they won't undergo automatic reconciliation. This grants users the freedom to make updates at their discretion.
Review Comment:
Suggested a different words because they are easier to understand to everyone :)
```suggestion
Knative resources are not watched by the operator, indicating they will not undergo automatic reconciliation. This grants users the freedom to make updates at their preference.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "domhanak (via GitHub)" <gi...@apache.org>.
domhanak merged PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#issuecomment-1988309605
🎊 PR Preview cca23820255a0d2a31d22ad053782e2aaada1fe0 has been successfully built and deployed. See the documentation preview: https://sonataflow-docs-preview-pr-570.surge.sh
<!-- Sticky Pull Request Comment -->
<!-- Sticky Pull Request Comment -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "kaldesai (via GitHub)" <gi...@apache.org>.
kaldesai commented on code in PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#discussion_r1520868773
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+{operator_name} can analyze the event definitions from the `spec.flow` and create `SinkBinding`/`Trigger` based on the type of the event. Then the workflow service can utilize them for event communications. The same purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here].
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a `KnativeEventing` CR.
+2. a broker named `default` is created. Currently all Triggers created by the {operator_name} will read events from `default`
Review Comment:
```suggestion
2. A broker named `default` is created. Currently all Triggers created by the {operator_name} will read events from `default`
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "RichardW98 (via GitHub)" <gi...@apache.org>.
RichardW98 commented on PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#issuecomment-1989136369
Thank you @ricardozanini ! please review again
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] doc for knative eventing in operator [incubator-kie-kogito-docs]
Posted by "ricardozanini (via GitHub)" <gi...@apache.org>.
ricardozanini commented on code in PR #570:
URL: https://github.com/apache/incubator-kie-kogito-docs/pull/570#discussion_r1520137208
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a KnativeEventing CR.
Review Comment:
```suggestion
1. Knative is installed on the cluster and Knative Eventing is initiated with a `KnativeEventing` CR.
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a KnativeEventing CR.
+2. a broker named `default` is created. Currently all Triggers created by Sonataflow operator will read events from `default`
Review Comment:
```suggestion
2. a broker named `default` is created. Currently all Triggers created by the {operator_name} will read events from `default`
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
Review Comment:
```suggestion
{operator_name} can analyze the event definitions from the `spec.flow` and create `SinkBinding`/`Trigger` based on the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here].
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a KnativeEventing CR.
+2. a broker named `default` is created. Currently all Triggers created by Sonataflow operator will read events from `default`
+
+== Configuring the workflow
+
+In order for operator to create the `SinkBinding` resources, the workflow must provide the sink information in `spec.sink`.
+
+.Example of a workflow with events
+[source,yaml]
+--
+apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlow
+metadata:
+...
+spec:
+ sink:
+ ref:
+ name: default
+ namespace: greeting
+ apiVersion: eventing.knative.dev/v1
+ kind: Broker
+ flow:
+ events:
Review Comment:
```suggestion
events: <2>
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a KnativeEventing CR.
+2. a broker named `default` is created. Currently all Triggers created by Sonataflow operator will read events from `default`
+
+== Configuring the workflow
+
+In order for operator to create the `SinkBinding` resources, the workflow must provide the sink information in `spec.sink`.
Review Comment:
```suggestion
For the operator to create the `SinkBinding` resources, the workflow must provide the sink information in `spec.sink`.
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a KnativeEventing CR.
+2. a broker named `default` is created. Currently all Triggers created by Sonataflow operator will read events from `default`
+
+== Configuring the workflow
+
+In order for operator to create the `SinkBinding` resources, the workflow must provide the sink information in `spec.sink`.
+
+.Example of a workflow with events
+[source,yaml]
+--
+apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlow
+metadata:
+...
+spec:
+ sink:
+ ref:
+ name: default
+ namespace: greeting
+ apiVersion: eventing.knative.dev/v1
+ kind: Broker
+ flow:
+ events:
+ - name: requestQuote
+ type: kogito.sw.request.quote
+ kind: produced
+ - name: aggregatedQuotesResponse,
+ type: kogito.loanbroker.aggregated.quotes.response,
+ kind: consumed,
+ source: /kogito/serverless/loanbroker/aggregator
+...
+--
+* `spec.sink.ref` defines the sink that all created sinkBinding will use as the destination sink for producing events
+* `spec.flow.events` lists all the events referenced in the workflow. Events with `produced` kind will trigger the creation of `SinkBindings` by the Sonataflow operator, while those labeled as `consumed` will lead to the generation of `Triggers`.
Review Comment:
```suggestion
<1> `spec.sink.ref` defines the sink that all created sinkBinding will use as the destination sink for producing events
<2> `spec.flow.events` lists all the events referenced in the workflow. Events with `produced` kind will trigger the creation of `SinkBindings` by the {operator_name}, while those labeled as `consumed` will lead to the generation of `Triggers`.
```
##########
serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-knative-eventing-resources.adoc:
##########
@@ -0,0 +1,59 @@
+= Knative Eventing
+:compat-mode!:
+// Metadata:
+:description: Configuration of knatve eventing deployed by the operator
+:keywords: kogito, sonataflow, workflow, serverless, operator, kubernetes, knative, knative-eventing, events
+
+This document describes how you can configure the workflows to let operator create the knative eventing resources on Kubernetes.
+
+Sonataflow can analyze the event definitions from `spec.flow` and create `SinkBinding`/`Trigger` based the type of the event. Then the workflow service can utilize them for event communications. The purpose of this feature in quarkus extension can be found xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc#ref-example-sw-event-definition-knative[here]
+
+== Prerequisite
+1. Knative is installed on the cluster and Knative Eventing is initiated with a KnativeEventing CR.
+2. a broker named `default` is created. Currently all Triggers created by Sonataflow operator will read events from `default`
+
+== Configuring the workflow
+
+In order for operator to create the `SinkBinding` resources, the workflow must provide the sink information in `spec.sink`.
+
+.Example of a workflow with events
+[source,yaml]
+--
+apiVersion: sonataflow.org/v1alpha08
+kind: SonataFlow
+metadata:
+...
+spec:
+ sink:
+ ref:
Review Comment:
```suggestion
ref: <1>
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org