You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2022/01/10 13:11:32 UTC

[camel-kamelets] 02/02: Extract Field Action: Add the possibility of setting the header name in case of headerOutput is true

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

acosentino pushed a commit to branch ex-field-improvements
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git

commit 6cea257030cd8945b49a004f2b65565cb4e5b510
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Jan 10 14:08:09 2022 +0100

    Extract Field Action: Add the possibility of setting the header name in case of headerOutput is true
---
 kamelets/extract-field-action.kamelet.yaml                           | 5 ++++-
 .../src/main/resources/kamelets/extract-field-action.kamelet.yaml    | 5 ++++-
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/kamelets/extract-field-action.kamelet.yaml b/kamelets/extract-field-action.kamelet.yaml
index f5e2038..32e83b8 100644
--- a/kamelets/extract-field-action.kamelet.yaml
+++ b/kamelets/extract-field-action.kamelet.yaml
@@ -38,7 +38,10 @@ spec:
 
       The optional parameter headerOutput allows the user to specify wheter the extracted field should be stored in a message header named 'CamelKameletsExtractFieldName', leaving the message body untouched.
 
-      The headerOutput is particulary useful in case you would like to reuse an extracted field as parameters for another header, for example.
+      The optional parameter headerOutputName allows the user to specify a custom header name instead of the default 'CamelKameletsExtractFieldName'. This parameter must be used in conjunction with headerOutput. 
+      If no headerOutputName parameter will be provided, the default 'CamelKameletsExtractFieldName' will be used.
+
+      The headerOutput/headerOutputName parameters are particulary useful in case you would like to reuse an extracted field as parameter for another header, for example.
     required:
       - field
     properties:
diff --git a/library/camel-kamelets/src/main/resources/kamelets/extract-field-action.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/extract-field-action.kamelet.yaml
index f5e2038..32e83b8 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/extract-field-action.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/extract-field-action.kamelet.yaml
@@ -38,7 +38,10 @@ spec:
 
       The optional parameter headerOutput allows the user to specify wheter the extracted field should be stored in a message header named 'CamelKameletsExtractFieldName', leaving the message body untouched.
 
-      The headerOutput is particulary useful in case you would like to reuse an extracted field as parameters for another header, for example.
+      The optional parameter headerOutputName allows the user to specify a custom header name instead of the default 'CamelKameletsExtractFieldName'. This parameter must be used in conjunction with headerOutput. 
+      If no headerOutputName parameter will be provided, the default 'CamelKameletsExtractFieldName' will be used.
+
+      The headerOutput/headerOutputName parameters are particulary useful in case you would like to reuse an extracted field as parameter for another header, for example.
     required:
       - field
     properties: