davsclaus opened a new pull request, #25982:
URL: https://github.com/apache/camel/pull/25982
## Backport of #25846
Cherry-pick of #25846 onto `camel-4.22.x`.
**Original PR:** #25846 - CAMEL-24464: Clarify exec control headers require
allowControlHeaders
**Original author:** @atiaomar1978-hub
**Target branch:** `camel-4.22.x`
### Original description
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`).
- Document that all `CamelExecCommand*` / `CamelExecExitValues` /
`CamelExecUseStderrOnEmptyStdout`
in-headers require `allowControlHeaders=true` (Java `@Metadata`, generated
catalog, and
`exec-component.adoc`).
- Log a once-per-endpoint 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.
See #25846 for full details and test coverage.
### Note on this backport
This is a straight cherry-pick of the squash-merge commit, except for one
adjustment: the original
PR added an upgrade-guide entry to `camel-4x-upgrade-guide-4_23.adoc` (main
only). Since that file
doesn't exist on `camel-4.22.x`, the equivalent entry was instead added to
the existing
`== Upgrading from 4.22.0 to 4.22.1` section of
`camel-4x-upgrade-guide-4_22.adoc` on this branch.
Per project convention, a follow-up will sync this entry into
`camel-4x-upgrade-guide-4_22.adoc` on
`main` as well.
_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]
