I want to be able to use connectors in my processes without any extra configuration.
Using connectors is a common use case. As Run is designed to be used by non-Java experts, it should be possible to use connectors without having to add Java libraries.
- With a default Run installation, I can deploy a process that uses an http or soap connector (https://docs.camunda.org/manual/7.13/user-guide/process-engine/connectors/#use-connectors) and it can be executed successfully
- As Run is based on the Spring Boot starter, what is required is to add the necessary dependencies to the classpath. The starter will then pick those up automatically and configure the connect engine plugin.
- With https://jira.camunda.com/browse/CAM-12158, we already have connect in Run. What is missing is the connect plugin.
Original description by reporter
I got hit by this after switch from tomcat to run, with a confusing error message (CAM-4292).
I propose to add at least camunda-connect-http-client to the base run distribution.
For additional connectors, I think something like run-full can be considered. Or alternatively, ship run without connectors and include all connectors in run-full.
Also please add documentation in https://docs.camunda.org/manual/latest/user-guide/camunda-bpm-run/ on how to add connectors (both from Camunda and custom).
Our experience with Camunda BPM Run: https://about.lovia.life/docs/infrastructure/camunda/