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

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

commit c15ca5d1eaeabf80e0f087e09535ff65e6b2e0ea
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Wed Jan 15 15:45:00 2025 +0100

    Kamelets Catalog - Make the description a one liner - AWS S3 Event based 
Source
    
    Signed-off-by: Andrea Cosentino <anco...@gmail.com>
---
 .../ROOT/partials/aws-s3-event-based-source-description.adoc  | 11 +++++++++++
 kamelets/aws-s3-event-based-source.kamelet.yaml               | 10 +---------
 .../resources/kamelets/aws-s3-event-based-source.kamelet.yaml | 10 +---------
 3 files changed, 13 insertions(+), 18 deletions(-)

diff --git 
a/docs/modules/ROOT/partials/aws-s3-event-based-source-description.adoc 
b/docs/modules/ROOT/partials/aws-s3-event-based-source-description.adoc
new file mode 100644
index 00000000..01a9c01a
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-s3-event-based-source-description.adoc
@@ -0,0 +1,11 @@
+== AWS S3 Event based Source Kamelet Description
+
+=== Authentication methods
+
+Access Key/Secret Key are the basic method for authenticating to the AWS SQS 
Service.
+
+=== Required Setup
+
+To use this Kamelet you'll need to set up Eventbridge on your bucket and 
subscribe Eventbridge bus to an SQS Queue.
+      
+For doing this you'll need to enable Evenbridge notification on your bucket 
and creating a rule on Eventbridge console related to all the events on S3 
bucket and pointing to the SQS Queue specified as parameter in this Kamelet.
diff --git a/kamelets/aws-s3-event-based-source.kamelet.yaml 
b/kamelets/aws-s3-event-based-source.kamelet.yaml
index 396d3508..a3c52478 100644
--- a/kamelets/aws-s3-event-based-source.kamelet.yaml
+++ b/kamelets/aws-s3-event-based-source.kamelet.yaml
@@ -33,15 +33,7 @@ metadata:
 spec:
   definition:
     title: AWS S3 Event Based Source
-    description: >-
-      Receive data from AWS SQS subscribed to Eventbridge Bus reporting events 
related to an S3 bucket or multiple buckets.
-
-      Access Key/Secret Key are the basic method for authenticating to the AWS
-      SQS Service.
-
-      To use this Kamelet you'll need to set up Eventbridge on your bucket and 
subscribe Eventbridge bus to an SQS Queue.
-      
-      For doing this you'll need to enable Evenbridge notification on your 
bucket and creating a rule on Eventbridge console related to all the events on 
S3 bucket and pointing to the SQS Queue specified as parameter in this Kamelet.
+    description: Receive data from AWS SQS subscribed to Eventbridge Bus 
reporting events related to an S3 bucket or multiple buckets.
     required:
       - accessKey
       - secretKey
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
index 396d3508..a3c52478 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/aws-s3-event-based-source.kamelet.yaml
@@ -33,15 +33,7 @@ metadata:
 spec:
   definition:
     title: AWS S3 Event Based Source
-    description: >-
-      Receive data from AWS SQS subscribed to Eventbridge Bus reporting events 
related to an S3 bucket or multiple buckets.
-
-      Access Key/Secret Key are the basic method for authenticating to the AWS
-      SQS Service.
-
-      To use this Kamelet you'll need to set up Eventbridge on your bucket and 
subscribe Eventbridge bus to an SQS Queue.
-      
-      For doing this you'll need to enable Evenbridge notification on your 
bucket and creating a rule on Eventbridge console related to all the events on 
S3 bucket and pointing to the SQS Queue specified as parameter in this Kamelet.
+    description: Receive data from AWS SQS subscribed to Eventbridge Bus 
reporting events related to an S3 bucket or multiple buckets.
     required:
       - accessKey
       - secretKey

Reply via email to