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-k-examples.git
The following commit(s) were added to refs/heads/main by this push: new 9e94e15 AWS S3 to Log: Fixed README (#36) 9e94e15 is described below commit 9e94e157dde8c18efe437483796a3e9f5daedda5 Author: Andrea Cosentino <anco...@gmail.com> AuthorDate: Fri Jul 2 13:24:42 2021 +0200 AWS S3 to Log: Fixed README (#36) --- kamelets/aws-s3-to-log/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/kamelets/aws-s3-to-log/README.md b/kamelets/aws-s3-to-log/README.md index 3840d12..e881808 100644 --- a/kamelets/aws-s3-to-log/README.md +++ b/kamelets/aws-s3-to-log/README.md @@ -4,15 +4,15 @@ - The Log Sink Kamelet is not available out of the box in 1.5.0 Camel-K release so you'll have to install it before installing the flow binding. -- If camel-k has been installed in a specific namespace different from the default one, you'll need to add a parameter to all the command (-n <namespace_name>)s +- If camel-k has been installed in a specific namespace different from the default one, you'll need to add a parameter to all the command (-n <namespace_name>) - Run the following commands - kubectl apply -f log-sink.kamelet.yaml - kubectl apply -f flow-binding.yaml + - kubectl apply -f log-sink.kamelet.yaml + - kubectl apply -f flow-binding.yaml - Check logs - kamel logs aws-s3-to-log + - kamel logs aws-s3-to-log - If you have files on your S3 bucket you should see their content consumed and the file in the bucket deleted