You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2026/08/31 20:21:22 UTC
(camel) 01/01: CAMEL-24464: Sync 4.22 upgrade guide with camel-4.22.x backport
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch doc-sync/CAMEL-24464-upgrade-guide-4_22
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 50c439f7b22d067915869ac3601aa5ed7139153a
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Mon Aug 31 22:21:02 2026 +0200
CAMEL-24464: Sync 4.22 upgrade guide with camel-4.22.x backport
Backport #25982 to camel-4.22.x added a camel-exec entry to that
branch's upgrade guide for the 4.22.0 to 4.22.1 section. Per the
upgrade-guide policy, main hosts the canonical copy of every
numbered guide, so mirror the same entry here.
Co-authored-by: Claude Sonnet 5 <no...@anthropic.com>
Signed-off-by: Claus Ibsen <cl...@gmail.com>
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
index 4eacfff6bdc3..91118ac92bf5 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
@@ -13,6 +13,18 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation] page for details.
== Upgrading from 4.22.0 to 4.22.1
+=== camel-exec
+
+`allowControlHeaders` is now annotated `security = "insecure:dev"`.
+With `camel.main.profile = prod` the default policy for that category is `fail`,
+so an endpoint or component that sets `allowControlHeaders=true` will not start
+unless you relax `camel.security.insecureDevPolicy`.
+
+When the flag is `false` (the default), any remaining `CamelExecCommand*`,
+`CamelExecExitValues`, or `CamelExecUseStderrOnEmptyStdout` headers are ignored
+and a WARN is logged once per exec endpoint. Those headers never overrode the
+URI without the flag; they were just silent before.
+
=== camel-ftp, camel-sftp, camel-ftps, camel-mina-sftp, camel-azure-files, camel-smb
The remote-file consumers now ensure the path resolved for a polled file stays within the directory being