Claus Ibsen created CAMEL-26792:
-----------------------------------
Summary: camel-jbang - a chaos experiment says why a route cannot
be fed, and warns when the feed goes to a real system
Key: CAMEL-26792
URL: https://issues.apache.org/jira/browse/CAMEL-26792
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
The feed of a chaos experiment ({{camel cmd chaos-experiment --feed}}, the
chaos_experiment tool, CAMEL-26786) is sent like {{camel cmd send}}: to the
endpoint the route starts from, with a producer. That reaches the route for
direct, seda, a stub (such as {{--stub=kafka}}) and a broker, but not for a
route that starts from:
* a timer, scheduler, cron or quartz: the route makes its own messages, so the
feed should be left out;
* an HTTP server (platform-http, the REST DSL, servlet, netty-http, undertow,
jetty): the component has no producer, or its producer is an HTTP client;
* another component that only consumes.
Today the experiment then fails with a producer error such as "Producer is not
supported", which says nothing to the AI or the user. The experiment should
refuse such a feed up front, with the reason and what to do instead (the
catalog tells whether a component only consumes, and its labels whether it
schedules or serves HTTP).
And a feed to a remote endpoint that is not stubbed goes to the real system (a
Kafka broker, a JMS queue): the experiment should warn, and say to stub it
({{--stub=kafka}}) or to run a local one ({{camel infra run kafka}}).
Follow-ups: feeding an HTTP route with HTTP requests to the integration's own
server, and naming the files of a file feed.
_Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
