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 2020/08/03 06:33:13 UTC

[camel-kafka-connector-examples] 01/01: We don't need a minio instance in move after read example

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

acosentino pushed a commit to branch fixed-s3-move-after-read
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector-examples.git

commit 4decd341c71419211cfde7325a951a463f098ff1
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Aug 3 08:32:37 2020 +0200

    We don't need a minio instance in move after read example
---
 aws2-s3/aws2-s3-move-after-read/README.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/aws2-s3/aws2-s3-move-after-read/README.adoc b/aws2-s3/aws2-s3-move-after-read/README.adoc
index 057067a..cf5dfd2 100644
--- a/aws2-s3/aws2-s3-move-after-read/README.adoc
+++ b/aws2-s3/aws2-s3-move-after-read/README.adoc
@@ -6,7 +6,7 @@ This is an example for Camel-Kafka-connector AW2-S3 with move after read option
 
 ## What is needed
 
-- A MinIO instance running
+- Your AWS credentials
 
 ## Running Kafka