[
https://issues.apache.org/jira/browse/CAMEL-26479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18140633#comment-18140633
]
Claus Ibsen commented on CAMEL-26479:
-------------------------------------
Taking this over, as part of the chaos work (no PR or branch for it after six
days).
Plan:
* Spring Boot: {{camel run --runtime=spring-boot --chaos}} adds plain
camel-chaos (no starter is needed: the ContextServicePlugin loads from the
classpath, and camel-spring-boot-dependencies manages it), and switches chaos
on with {{-Dcamel.chaos.enabled=true}} in the JVM arguments of the run, unless
the profile is prod. The scenario ({{--chaos=file}}) and {{--chaos-report}} are
passed the same way. Nothing is written into the exported project, so an
exported project never has chaos on. An existing Spring Boot project (camel run
pom.xml) gets camel-chaos in its temporary run pom.
* Quarkus: still refused for now. camel-chaos is new in Camel 4.24, and the
latest Camel Quarkus (3.40.0) is on an older Camel, so the run would mix
camel-chaos 4.24 with an older camel-core. It can follow once Camel Quarkus is
on 4.24 (and a camel-quarkus-chaos extension would be needed for native mode).
_Claude Code on behalf of Claus Ibsen_
> camel-jbang - camel run --chaos for the Spring Boot and Quarkus runtimes
> ------------------------------------------------------------------------
>
> Key: CAMEL-26479
> URL: https://issues.apache.org/jira/browse/CAMEL-26479
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: shashank
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Follow-up of CAMEL-26436 (apache/camel#28788), named by Claus in that ticket
> after the merge.
> {{camel run --chaos}} adds camel-chaos to a run with the Camel Main and JBang
> runtimes, and the CLI connector, {{camel cmd chaos-*}}, {{camel get chaos}}
> and the dev console then work as described on the chaos page. With
> {{--runtime=spring-boot}} and {{--runtime=quarkus}} the option is refused for
> now ({{CliException}} with a usage message), because the run of those
> runtimes exports a project and builds it with Spring Boot or Quarkus, and two
> things are missing there:
> * camel-chaos is not added to the exported project;
> * chaos only switches on with Camel profile {{dev}} or
> {{camel.chaos.enabled=true}} (never with profile {{prod}}), and the exported
> project does not get either.
> {{design/chaos.adoc}} ("Getting it") says the same.
> *Proposal*
> * {{camel run --chaos}} with {{--runtime=spring-boot}} and
> {{--runtime=quarkus}}: add the chaos dependency to the exported project (the
> artifact each runtime uses for Camel components) and switch chaos on in the
> exported configuration the way that runtime sets the Camel profile for
> development, so that chaos stays off with profile {{prod}} as on the other
> runtimes.
> * Check what each runtime needs to load the camel-chaos
> {{ContextServicePlugin}} (plain classpath, a Spring Boot starter, or a
> Quarkus extension). If a starter or an extension is needed, it belongs to
> camel-spring-boot or camel-quarkus; this ticket then covers the camel-jbang
> side and links the issues there.
> * Tests in camel-jbang for the export of both runtimes (the dependency and
> the configuration), and the chaos page and the design doc updated.
> _Filed with Claude Code on behalf of allthingssecurity._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
