davsclaus opened a new pull request, #29567:
URL: https://github.com/apache/camel/pull/29567
The run options form (F2 > Run an example..., Run from folder..., and
running a Maven project) gets a *Chaos testing* checkbox, which adds `--chaos`
to `camel run`, so camel-chaos is installed and rules can be added while the
integration runs (Chaos tab, `camel cmd chaos-add`).
- All runtimes take it (Camel Main, Spring Boot, Quarkus, JBang, Maven
projects), as they all go through `camel run`.
- With profile prod camel-chaos stays off, so the row is greyed out ("not
available with profile prod") and `--chaos` is not passed.
- The checkbox is the last row of the options page; the moves to and from
the properties page that assumed JFR was the last row now use `ROW_LAST`.
- Docs: the getting-started page lists the option, and the Chaos section of
the observe page says where to turn it on.
Tests: `RunOptionsFormTest` covers off by default, ticking adds `--chaos`,
not passed with profile prod, and no toggle while prod is selected; the module
tests pass. Tried by hand: the timer-log example started from the form with the
box ticked shows chaos on in the header, and a rule injects its faults.
Follow-up: [CAMEL-26814](https://issues.apache.org/jira/browse/CAMEL-26814),
pick a chaos scenario (`--chaos=test/chaos/<name>.chaos`) and run the Citrus
tests of an example from the same form.
_Claude Code on behalf of davsclaus_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_012nJsFsjqqFiwroeHRWaKbS
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
