Our system runs on Camunda 7, using only the Camunda engine with BPMN containing service tasks and message events. We retrieve data from a custom extension element in service tasks.
As we migrate to Camunda 8, custom elements are unsupported, so we’re switching to task headers. Since task headers only support key-value pairs, we store multiple values as a JSON string. However, this requires significant code changes. A better alternative would be manually parsing the XML file to extract data.
We avoid using Operate because:
-
From version 8.6, both Zeebe and Operate are paid. While we may pay for Zeebe, Operate adds extra costs.
-
In Camunda 7, we used engine APIs instead of an external tool. In Camunda 8,If we use operate it would require an additional container just for one API call. Fetching the XML from Zeebe or Elasticsearch would optimize deployment.
-
to call Operate API we need authentication method,If it is like we just add demo, demo in parameters of operate API and it allow api call than also it is fine but here it is via cookie or via token, but all these operate api call in our system will be internal call so we don’t want authentication and we didn’t find any option to remove authentication,
Additionally, I need help understanding how to delete a deployment definition.
I came across this forum post: Camunda 8 delete deployed process, where it was mentioned that deleting a deployment is not possible. However, Niall referenced a Camunda blog which is edited now and states that deployment deletion is now possible using Operate. see it here
If possible Could you please help me understand which internal API Operate calls to delete a deployment?