Ubuntu 24.04.1 LTS
SM Camunda Version 8 deployed via Helm Chart
All pods are running
Hello,
Sorry for long post.
I’m trying to evaluate SM Camunda and I have deployed it successfully on my desktop ubuntu server.
I was able create a bpmn process file
bpmn has simple webhook start event to trigger the process with activate condition set
A task with outbound rest connector to invoke an external service.
Since I was not able deploy/publish from web modeler, I deployed the bpmn file from client zbctl
From zbctl, I’m able to
Deploy the process file
Run the process sucessfully
The issue is that I’m not able to invoke the process via webhook REST call.
From what I understand, webhook should also be deployed/published to process engine. I tried to upload the webhook connector json file but zbctl gave error that file is unkown format
One more thing to note which might be relevant, I’m able to “hit” the REST API’s on camunda zeebe gateway from postman (v1/topology, v1/process-instances/:key) with token generated from keycloak
Would appreciate if someone can shed some light on this issue.
I would like to publish webhook connector either via zbctl or via web modeler.
Via web modeler, I’m facing http2 exception when modeler tries to connect to zeebe gateway. I tried setting up ssl for nginx as mentioned in one of the tutorial but still getting http2 exception
Camunda components are running in kubernetes pods, while web modeler is running as docker container. I’m using kube portforwards and iptables to connect to web modeler to zeebe gateway
Via zbctl client, I can only upload bpmn file. My understanding is that webhook connector needs separate deployment to processing engine (zeebe), how can I do that?
Here is my zbctl status
zbctl status --insecure
2024/09/02 14:43:45 Warning: The configured security level does not guarantee that the credentials will be confidential. If this unintentional, please enable transport security.
I recommend not using an activationCondition, until you can call your webhook at least. Then you can try adding the condition back.
The URL depends on where you try to call the webhook. localhost would work only from the connectors pod, otherwise you need to use the service name to reach the pod.
How did you try to call this endpoint? And from where?