[ 
https://issues.apache.org/jira/browse/CAMEL-26479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-26479 started by shashank.
----------------------------------------
> 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: shashank
>            Priority: Minor
>
> 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)

Reply via email to