This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit 8cfdf2b3b05f2e88310e7e76d75aab3b682dc0c5
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Thu Mar 24 14:57:09 2022 +0100
AWS S3 Sink: Add an optional keyName parameter
---
.../src/main/resources/kamelets/aws-s3-sink.kamelet.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml
index 5b5a492..5838d29 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-sink.kamelet.yaml
@@ -37,11 +37,11 @@ spec:
When using a default Credentials Provider the S3 client will load the
credentials through this provider and won't use the static credential. This is
reason for not having the access key and secret key as mandatory parameter for
this Kamelet.
- The Kamelet expects the following headers to be set:
+ The Kamelet can use the following header to be set:
- `file` / `ce-file`: as the file name to upload
- If the header won't be set the exchange ID will be used as file name.
+ If the header won't be set, the Kamelet parameter `keyName` should be
populated. The `keyName` parameter could be a simple value language from the
Apache Camel.
required:
- bucketNameOrArn
- region
