[
https://issues.apache.org/jira/browse/CAMEL-26786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26786.
---------------------------------
Resolution: Fixed
Merged in https://github.com/apache/camel/pull/29499 (4a2b40ad6a90).
_Claude Code on behalf of davsclaus_
> camel-jbang - camel cmd chaos-experiment: one experiment in one call, with
> its traffic and the wait for its verdict
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26786
> URL: https://issues.apache.org/jira/browse/CAMEL-26786
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> Step 5 of CAMEL-26760 ("let there be chaos"), part 2: one experiment per
> call, after the experiments in the journal (CAMEL-26774) and camel cmd send
> --repeat (CAMEL-26767).
> * {{camel cmd chaos-explore-start}} and {{chaos-explore-finish}}: start an
> exploration with a budget and a focus, and finish it before its deadline (by
> hand; {{camel cmd chaos-explore}} with an AI comes in step 6).
> * {{camel cmd chaos-experiment}}: one experiment in one call. It begins the
> experiment (hypothesis and rules), sends the traffic when a feed is given
> ({{--feed=<endpoint> --body --repeat --interval}}, as camel cmd send), waits
> until the expectations are decided or {{--wait}} is up, ends it, and prints
> what came of it: the verdict, the expectations, the traffic sent, and the
> counts per route.
> * The same as tools for {{camel ask}} and the MCP server:
> {{chaos_explore_start}}, {{chaos_experiment}} and {{chaos_explore_finish}}
> ({{camel_runtime_chaos_*}} in MCP), so a small model runs an experiment in
> one call.
> _Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
