[ 
https://issues.apache.org/jira/browse/CAMEL-26722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18140404#comment-18140404
 ] 

Claus Ibsen commented on CAMEL-26722:
-------------------------------------

Merged in #29392 (1af51333af0a): scenario files, chaos-load, camel run 
--chaos=<file>, --chaos-report, the verdict as the exit code, and save as 
scenario on the chaos screen.

_Claude Code on behalf of Claus Ibsen_

> camel-chaos - scenario files and a verdict as the exit code of camel run
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-26722
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26722
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.24.0
>
>
> W-1 and W-2 of the stage 2 decisions on CAMEL-26607.
> *Scenarios (W-1)*
> * A file {{chaos/<name>.chaos}} in the project: one rule per line, {{#}} 
> comments, and a {{seed=}} line. The phases come from {{from=}}/{{until=}}.
> * {{camel cmd chaos-load <file>}} loads one into a running integration.
> * {{camel run --chaos=<file>}} starts with one ({{camel.chaos.scenario}} for 
> any Camel Main application).
> * {{camel run *}} and {{camel export}} skip {{.chaos}} files.
> * Save the current rules as a scenario from the chaos screen (a follow-up).
> *CI mode (W-2)*
> * A run with chaos ends with exit 0 on PASS and 1 on FAIL. Without 
> expectations there is no verdict: exit 0, and a line that says so.
> * {{--chaos-report=<file>}} writes the JSON report when the run ends 
> ({{camel.chaos.reportFile}}).



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to