This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch ex-field-strict-check in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit 6fbc1fc6e3c5ff04284f00f2c026a73d903426de Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Jan 10 14:46:44 2022 +0100 Extract Field Action: Sanitize/check the header name if set and avoid clashes --- kamelets/extract-field-action.kamelet.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/kamelets/extract-field-action.kamelet.yaml b/kamelets/extract-field-action.kamelet.yaml index 562952c..b13561f 100644 --- a/kamelets/extract-field-action.kamelet.yaml +++ b/kamelets/extract-field-action.kamelet.yaml @@ -41,7 +41,9 @@ spec: 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. + The optional parameter strictHeaderCheck allows to user to enable a strict header name check. If enabled the action will check if the header output name (custom or default) has been used already in the exchange. If so, the extracted field will be stored in the message body, if not, the extracted field will be stored in the selected header (custom or default). + + The headerOutput/headerOutputName/strictHeaderCheck parameters are particulary useful in case you would like to reuse an extracted field as parameter for another header, for example. required: - field properties: @@ -63,7 +65,7 @@ spec: type: string strictHeaderCheck: title: Strict Header Check - description: If enable the action will check if the header output name (custom or default) has been used already in the exchange. If so, the extracted field will be stored in the message body, if not, the extracted field will be stored in the selected header (custom or default). + description: If enabled the action will check if the header output name (custom or default) has been used already in the exchange. If so, the extracted field will be stored in the message body, if not, the extracted field will be stored in the selected header (custom or default). type: boolean default: false x-descriptors:
