atiaomar1978-hub opened a new pull request, #25846: URL: https://github.com/apache/camel/pull/25846
Fixes [CAMEL-24464](https://issues.apache.org/jira/browse/CAMEL-24464) ## Problem Since Camel 4.20 (CAMEL-23315), `CamelExecCommand*` in-headers only override URI options when `allowControlHeaders=true`. The component documentation still read as if those headers always worked, which misled users when the flag was left at its default (`false`). ## Solution - Document that all `CamelExecCommand*` / `CamelExecExitValues` / `CamelExecUseStderrOnEmptyStdout` in-headers require `allowControlHeaders=true` (Java `@Metadata`, generated catalog, and `exec-component.adoc`). - Log a **once-per-binding** WARN in `DefaultExecBinding` when control headers are present but ignored because `allowControlHeaders=false`. - Mark `allowControlHeaders` with `security = "insecure:dev"` and register it in `SecurityUtils` so `camel.main.profile=prod` blocks opt-in unless the policy is relaxed. - Add a 4.22 → 4.23 upgrade-guide entry for `camel-exec`. ## Testing ``` ./mvnw -pl components/camel-exec test ``` All tests pass. --- _Claude Code on behalf of atiaomar1978-hub_ -- 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]
