wmedvede commented on issue #348:
URL:
https://github.com/apache/incubator-kie-kogito-serverless-operator/issues/348#issuecomment-1887491582
Hi @dmartinol which setup are you doing? I mean, how are you deploying the
data-index.
The question is because as part of the OpenShift usecase I'm preparing,
that deploys both the data-index and jobs-service by using the
sonataflow-platform, I can see that the operator is now generating this
properties ni the workflow CM, which is good.
In fact, I can create a WF instance and see the expected information at the
data-index and the jobs-service.
```
kogito.events.usertasks.enabled = false
kogito.events.variables.enabled = false
kogito.events.processdefinitions.enabled = false
kogito.service.url = http://callbackstatetimeouts.test-platform2-oc
quarkus.http.port = 8080
quarkus.http.host = 0.0.0.0
org.kie.kogito.addons.knative.eventing.health-enabled = false
quarkus.devservices.enabled = false
quarkus.kogito.devservices.enabled = false
kogito.events.processinstances.enabled = true
mp.messaging.outgoing.kogito-job-service-job-request-events.connector =
quarkus-http
mp.messaging.outgoing.kogito-job-service-job-request-events.url =
http://sonataflow-platform-jobs-service.test-platform2-oc/v2/jobs/events
mp.messaging.outgoing.kogito-processinstances-events.url =
http://sonataflow-platform-data-index-service.test-platform2-oc/processes
```
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
