[I] cli-connector is enabled by default outside dev and test [camel-quarkus]

["oscerd (via GitHub)" <gi...@apache.org>]

oscerd opened a new issue, #9052:
URL: https://github.com/apache/camel-quarkus/issues/9052

   `extensions-jvm/cli-connector/.../CamelCliConnectorConfig.java:32`
   
   ```java
   @WithDefault("true")
   boolean enabled();
   ```
   
   `CliConnectorProcessor` applies no launch-mode condition — the only gate is this flag — and `CamelCliConnectorRecorder` unconditionally calls `factory.setEnabled(true)`. Only `sigterm()` handling is launch-mode aware. The connector's action-file IPC is therefore active in production builds.
   
   **Suggested fix**
   
   Gate it the way the console extension is gated — dev/test by default with an explicit opt-in for production — or flip the default to `false` outside dev/test.
   


-- 
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: commits-unsubscribe@camel.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] cli-connector is enabled by default outside dev and test [camel-quarkus]

["oscerd (via GitHub)" <gi...@apache.org>]

oscerd closed issue #9052: cli-connector is enabled by default outside dev and test
URL: https://github.com/apache/camel-quarkus/issues/9052


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] cli-connector is enabled by default outside dev and test [camel-quarkus]

["oscerd (via GitHub)" <gi...@apache.org>]

oscerd commented on issue #9052:
URL: https://github.com/apache/camel-quarkus/issues/9052#issuecomment-5494534118

   Closing along with PR #9069. Gating the CLI connector to dev/test would break `camel run --runtime=quarkus`, which launches via `quarkus:run` (prod mode) unless `--dev`/`--reload` is passed, so camel-jbang would lose the ability to interact with the running application. The connector's action-file IPC is local-only and same-user, so the insecure default it fixes is not a meaningful trust boundary. Revisiting this would mean changing camel-jbang to pass `-Dquarkus.camel.cli.exposure-mode=all` first. Details in PR #9069.


-- 
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: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org