davsclaus opened a new pull request, #26542:
URL: https://github.com/apache/camel/pull/26542

   Second and last part of 
[CAMEL-24661](https://issues.apache.org/jira/browse/CAMEL-24661), after #26532 
(execution limits and the Quarkus log file name).
   
   ## What
   
   `camel run --console` and `camel export --console` only enabled the 
developer console with Camel Main. Now:
   
   - **Spring Boot** (`ExportSpringBoot`): adds `camel-console-starter` and 
`camel-management-starter`, sets `camel.main.devConsoleEnabled=true`, and adds 
`camel` to `management.endpoints.web.exposure.include` — the console is the 
`camel` actuator endpoint at `/actuator/camel`. With `--observe` as well, 
`health,prometheus` are merged into the exposure list first, as the 
observability starter only contributes those as lowest-precedence defaults that 
an explicit list would replace; the console is then at `/observe/camel` on the 
management port. The hawtio block now shares the same `exposeActuatorEndpoints` 
helper.
   - **Quarkus** (`ExportQuarkus`): adds `camel-quarkus-console` and 
`camel-quarkus-management`, sets `camel.main.dev-console-enabled=true` and 
`quarkus.camel.console.exposure-mode=ALL` — the extension only exposes the 
console in dev/test mode by default and `camel run` without `--dev` runs via 
`quarkus:run` (prod mode). Console at `/q/camel/dev-console` (the extension's 
default path).
   - The console is enabled with the shared `camel.main.devConsoleEnabled` 
option on all three runtimes; only the Quarkus exposure mode is runtime 
specific.
   - `Run.runQuarkus()` / `runSpringBoot()` now pass `--observe` and 
`--console` on to the exporter (only `runCamelMain()` did), so `camel run 
--runtime=spring-boot --observe` also works now.
   - `--console` option descriptions on `run` and `export` (and the generated 
command docs / metadata) no longer say "Camel Main runtime only".
   
   Verified with a real `camel run hello.camel.yaml --console` per runtime: 
Spring Boot serves `/actuator/camel` and `/actuator/camel/routes`; Quarkus 
serves `/q/camel/dev-console` under `quarkus:run`; Spring Boot with `--console 
--observe` serves `/observe/camel`, `/observe/health` and `/observe/metrics` on 
port 9876.
   
   ## Tests
   
   `ExportTest.shouldExportConsoleForCamelMain` becomes the parameterized 
`shouldExportConsole` over all three runtimes (dependencies, 
`camel.main.devConsoleEnabled`, the exposure list / exposure mode, and that 
`camel.jbang.console` does not leak). New 
`shouldExposeConsoleWithObserveOnSpringBoot` and 
`shouldExposeConsoleWithHawtioOnSpringBoot` cover the exposure-list merging.
   
   ## Docs
   
   - `camel-jbang-managing.adoc`: Developer Console section lists the path per 
runtime and the Quarkus prod-mode exposure note.
   - `camel-jbang-running.adoc`: `--observe` and `--console` added to the 
options passed on all runtimes; the "not yet with Spring Boot and Quarkus" 
limitation is removed.
   - `camel-jbang-configuration.adoc`: `camel.jbang.console` description.
   
   _Claude Code on behalf of davsclaus_


-- 
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]

Reply via email to