As a remote consumer, I can subscribe to a stream of zeebe events published to a topic.

• Create an endpoint that subscribes a topicHandler and forwards the GeneralEvent

with zeebe:jobworker?name=foo

we can subscribe as "foo"

client side: send subscribe command
server side: create route that publishes and receives jobEvents

Future zeebe will drop the topic concept and rely on clients topic only.
So setting an optional topic is no longer required

single file for consumer/producer

on the client side: zeebe:startprocess?topic=x,processDefinitionKey=myProcess
body: initial payload

on the server side: start new instance

it is not possible to get the state from a generalEvent (see camunda/zeebe#367 ) but it is essential to have this in the message header for camel.
Until zeebe supports this, we have to extract the value from the json content.

When we subscribe with the universal event handler, we forward the zeebe events directly. They should be converted to zeebe-agnostic camel-zeebe-only pojos

via zeebe:deployment?topic=foo I can override the clients defaultTopic in case the DeployCommand does not define a topic

currently constant, introduce parameter

I want to deploy a process using camels from file consumer

Required: processor that transforms the file exchange to a deployCommand

in the component, wrap all required information (Client Supplier, uri, remaining, parameters) in a data class and pass it to endpoints.

When reading from file or writing to file, we need the body command/event to be serialized as json.

I see two options:

• use a typeConverter String/Pojo per command/event
• use (un)marshal.json(...) in the route

AC:

• every api command/event that is written to/read from file is converted from/to json

On the client side: create a deploy command and publish to route
on the server side: receive command and use fluent deployment api to publish process

currently constant, introduce parameter

introduced with camunda/zeebe#672

Today, the camel.api.jobevent is written to the exchange, it should be possible to toggle the behavior

The body just requires payload and customHeaders.

Introduce exchange wrapper/processor