Claus Ibsen created CAMEL-26761:
-----------------------------------
Summary: camel-chaos - keep chaos scenarios in test/chaos, which
camel run already leaves alone
Key: CAMEL-26761
URL: https://issues.apache.org/jira/browse/CAMEL-26761
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
Chaos scenarios live in {{chaos/<name>.chaos}} today (the TUI key {{s}} writes
there, and the docs and examples use it). Move them under {{test/chaos/}},
which Camel CLI already leaves alone:
* {{camel run --dev --source-dir}} watches the source dir recursively with the
reload pattern {{*,!test/**}} ({{RunPipeline.sourceDirReloadPattern}}).
{{chaos/}} is not excluded, so saving a scenario, and with CAMEL-26760 the feed
messages and reports an agent writes, land in a watched folder. A feed message
in .yaml or .xml could be read as a route.
* Citrus tests live in {{test/}} ({{camel test run}}), and {{camel run test/}}
refuses a folder of only Citrus tests. A scenario is a test too: a CI gate with
a verdict as the exit code. With CAMEL-26760 stage 2, Citrus can send the
traffic of a scenario from the same feed folder.
* No second reserved folder name.
Layout:
{noformat}
test/
orders.citrus.it.yaml
chaos/
payment-outage.chaos
refunds-fails.chaos
refunds-fails/ (CAMEL-26760: the feed of the scenario)
{noformat}
4.24 is not released yet, so no upgrade guide entry is needed.
_Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
