Claus Ibsen created CAMEL-26695:
-----------------------------------
Summary: camel-jbang - chaos screen: add, change and remove rules,
add from the known rules, and chaos from the diagram
Key: CAMEL-26695
URL: https://issues.apache.org/jira/browse/CAMEL-26695
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
The chaos screen (CAMEL-26608) shows the rules, their live state and the
report, and only reads. The next steps, from the design (sections 2 to 4 of
https://claude.ai/artifact/8nzJQAAjBpFWVKrexaoPZT), one PR each:
h3. 1. The actions
On the Chaos screen, through the {{chaos}} action of the CLI connector, as
{{camel cmd chaos-*}} does:
* {{a}} add a rule and {{e}} change the selected one, typed as a one-line rule
(the change starts from the rule as it is);
* {{x}} remove the selected rule, {{c}} clear all rules, {{R}} start a new
experiment ({{chaos-clear --reset}}: no rules, a new report, the same seed).
Each asks for confirmation with the rule shown, as the other actions that
change a running integration do; only the user answers it (not an MCP client or
a tape). A rule that is not valid comes back with the reason of the parser, and
a rule that matches nothing with its warnings, in a dialog from which the rule
can be changed.
h3. 2. Add from the known rules
The add dialog offers the recipes of the rule model in the catalog
(CAMEL-26689, {{CamelCatalog.chaosModelJSon()}}), grouped by what goes wrong
("Downstream returns an error", "Did the work, then failed", "The route flaps",
...), with a form for the placeholders: the endpoints, routes and steps are
picked from the integration (the {{pick}} of a placeholder), and the one-line
rule is shown as it is built. Only the recipes of camel-chaos for now; custom
recipes can come later.
h3. 3. Chaos from where you look
{{!}} on a node of the Diagram, an endpoint of the Endpoint tab or a consumer
opens the add dialog with the target filled in, and only the recipes whose
faults that node offers (the hooks of the model). The exchanges a rule faulted
({{CamelChaosRule}}, CAMEL-26678) get a 🎲 mark in Activity, Errors and Inspect,
so a failure made on purpose is not debugged as a real one.
Later, to be tried out first: Fix with AI and Explain with AI on a chaos-made
error, and the cause-and-effect chart (with the timeline, CAMEL-26691).
_Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
