This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 2ef8576dc7c4 CAMEL-26280: camel-azure-functions - add the 
invokeFunction note to the 4.22 upgrade guide (#29764)
2ef8576dc7c4 is described below

commit 2ef8576dc7c41351a9763d3a486425e98538d0c1
Author: Claus Ibsen <[email protected]>
AuthorDate: Fri Nov 13 08:02:13 2026 +0100

    CAMEL-26280: camel-azure-functions - add the invokeFunction note to the 
4.22 upgrade guide (#29764)
    
    Adds the CAMEL-26280 note (invokeFunction checks the function app and the
    function name) to the "Upgrading from 4.22.2 to 4.22.3" section of the 4.22
    guide on main, for the camel-4.22.x backport #29762. No 4.18 note:
    camel-azure-functions does not exist on camel-4.18.x.
    
    Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc       | 11 +++++++++++
 1 file changed, 11 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 f15d23fdd8d8..0e997d398009 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
@@ -82,6 +82,17 @@ scheduled time of its window, but before the (late) timer 
has run, joins that wi
 checkpointed by that timer. Before, such an event always started a new window, 
so `timeout` was practically never
 set. Routes that read this header can now see `timeout` as well as `size`.
 
+=== camel-azure-functions - invokeFunction checks the function app and the 
function name
+
+The `invokeFunction` operation now checks the function app and the function 
name, from the endpoint or from the
+`CamelAzureFunctionsFunctionApp` and `CamelAzureFunctionsFunctionName` 
headers, before it calls the function, and
+builds the URL with the function name encoded as a path. The exchange fails 
with an `IllegalArgumentException` when the
+function app is missing or is not an app name (letters, digits and hyphens, 
not starting or ending with a hyphen, at
+most 60 characters), or when the function name has a `?`, `#`, `\` or `%`, an 
empty segment, or a `.` or `..`
+segment. A function name of several segments, such as `products/42` for a 
function with a custom route, is still
+accepted. The `x-functions-key` header is only added to an `https` URL on an 
`azurewebsites.net` host. Valid
+configurations are not affected.
+
 === camel-hazelcast - the hazelcast-seda consumer restores a transferred 
exchange only with transferExchange=true
 
 A `hazelcast-seda` consumer now restores the headers and exchange properties 
of an exchange that a producer with

Reply via email to