oscerd opened a new pull request, #9070: URL: https://github.com/apache/camel-quarkus/pull/9070
Fixes #9057. `ConsoleProcessor.canExposeManagementEndpoint` returns true for `exposure-mode=ALL` regardless of launch mode. That is intentional — it is the documented way to expose the console in prod, and the default is `DEV_TEST` — but `usage.adoc` explained how to turn it on without saying what it exposes. This adds two things to the existing "Exposing the developer console in prod mode" section: - The console authenticates nobody, and what the consoles actually disclose — route and endpoint configuration, in-flight and recent exchange data, JVM and environment details, and the application's own configuration values. - The route is registered via `nonApplicationRootPathBuildItem...management()`. Quarkus non-application endpoints are served on the **main** HTTP port under `/q/` unless `quarkus.management.enabled=true`, so by default the console shares the socket serving application traffic rather than sitting on a port that can be firewalled separately. That is the part most likely to surprise an operator who assumed `/q/` meant a management port. **Documentation only — no behaviour change.** The gate is untouched; `exposure-mode=ALL` remains an explicit operator opt-in, which is out of scope as a vulnerability under the Camel security model. I did not add a second acknowledgement property as the issue floated. `exposure-mode=ALL` is already an explicit opt-in, and a second flag to confirm the first buys little for the friction it adds. Every property referenced in the new text was checked against the generated reference page — the console extension has exactly three options (`enabled`, `path`, `exposure-mode`), and `quarkus.management.enabled` is a stock Quarkus one. `./mvnw clean validate -pl docs` passes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
