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 2025/01/27 09:54:08 UTC
(camel-kamelets) branch main updated (ba00c8dc -> 9d791877)
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
from ba00c8dc Bump golang.org/x/net from 0.23.0 to 0.33.0 in /script/generator (#2366)
new 164337a7 Kamelets Catalog - Make the description a one liner - AWS Secrets Manager Sink
new 6af3ad6e Kamelets Catalog - Make the description a one liner - AWS SES Sink
new 9d791877 Kamelets Catalog - Make the description a one liner - AWS SNS Fifo Sink
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
...on.adoc => aws-secrets-manager-sink-description.adoc} | 7 +++++--
...nk-description.adoc => aws-ses-sink-description.adoc} | 12 ++++++++----
...scription.adoc => aws-sns-fifo-sink-description.adoc} | 4 ++--
kamelets/aws-secrets-manager-sink.kamelet.yaml | 13 +------------
kamelets/aws-ses-sink.kamelet.yaml | 16 +---------------
kamelets/aws-sns-fifo-sink.kamelet.yaml | 11 +----------
.../kamelets/aws-secrets-manager-sink.kamelet.yaml | 13 +------------
.../main/resources/kamelets/aws-ses-sink.kamelet.yaml | 16 +---------------
.../resources/kamelets/aws-sns-fifo-sink.kamelet.yaml | 11 +----------
9 files changed, 21 insertions(+), 82 deletions(-)
copy docs/modules/ROOT/partials/{aws-ec2-sink-description.adoc => aws-secrets-manager-sink-description.adoc} (86%)
copy docs/modules/ROOT/partials/{aws-eventbridge-sink-description.adoc => aws-ses-sink-description.adoc} (69%)
copy docs/modules/ROOT/partials/{aws-ec2-sink-description.adoc => aws-sns-fifo-sink-description.adoc} (90%)
(camel-kamelets) 03/03: Kamelets Catalog - Make the description a one liner - AWS SNS Fifo Sink
Posted by ac...@apache.org.
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 9d7918771b3621f5e99e32b988561032b4dd3854
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Jan 27 10:48:26 2025 +0100
Kamelets Catalog - Make the description a one liner - AWS SNS Fifo Sink
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../partials/aws-sns-fifo-sink-description.adoc | 26 ++++++++++++++++++++++
kamelets/aws-sns-fifo-sink.kamelet.yaml | 11 +--------
.../kamelets/aws-sns-fifo-sink.kamelet.yaml | 11 +--------
3 files changed, 28 insertions(+), 20 deletions(-)
diff --git a/docs/modules/ROOT/partials/aws-sns-fifo-sink-description.adoc b/docs/modules/ROOT/partials/aws-sns-fifo-sink-description.adoc
new file mode 100644
index 00000000..3706ca0e
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-sns-fifo-sink-description.adoc
@@ -0,0 +1,26 @@
+== AWS SNS FIFO Sink Kamelet Description
+
+=== Authentication methods
+
+In this Kamelet you have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of access key/secret key or default credentials provider could be used
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+=== Required Headers
+
+The Kamelet expects the following headers to be set:
+
+- `subject` / `ce-subject`: the subject of the message
diff --git a/kamelets/aws-sns-fifo-sink.kamelet.yaml b/kamelets/aws-sns-fifo-sink.kamelet.yaml
index d07d4921..43ea47cf 100644
--- a/kamelets/aws-sns-fifo-sink.kamelet.yaml
+++ b/kamelets/aws-sns-fifo-sink.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: AWS SNS FIFO Sink
- description: |-
- Send message to an AWS SNS FIFO Topic.
-
- Access Key/Secret Key are the basic method for authenticating to the AWS SNS Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the SNS 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:
-
- - `subject` / `ce-subject`: the subject of the message
+ description: Send message to an AWS SNS FIFO Topic.
required:
- topicNameOrArn
- region
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-sns-fifo-sink.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-sns-fifo-sink.kamelet.yaml
index d07d4921..43ea47cf 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-sns-fifo-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-sns-fifo-sink.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: AWS SNS FIFO Sink
- description: |-
- Send message to an AWS SNS FIFO Topic.
-
- Access Key/Secret Key are the basic method for authenticating to the AWS SNS Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the SNS 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:
-
- - `subject` / `ce-subject`: the subject of the message
+ description: Send message to an AWS SNS FIFO Topic.
required:
- topicNameOrArn
- region
(camel-kamelets) 02/03: Kamelets Catalog - Make the description a one liner - AWS SES Sink
Posted by ac...@apache.org.
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 6af3ad6efaea8e8599e729c9879ca967ed9b57fc
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Jan 27 10:33:36 2025 +0100
Kamelets Catalog - Make the description a one liner - AWS SES Sink
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../ROOT/partials/aws-ses-sink-description.adoc | 32 ++++++++++++++++++++++
kamelets/aws-ses-sink.kamelet.yaml | 16 +----------
.../resources/kamelets/aws-ses-sink.kamelet.yaml | 16 +----------
3 files changed, 34 insertions(+), 30 deletions(-)
diff --git a/docs/modules/ROOT/partials/aws-ses-sink-description.adoc b/docs/modules/ROOT/partials/aws-ses-sink-description.adoc
new file mode 100644
index 00000000..42bdfbf4
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-ses-sink-description.adoc
@@ -0,0 +1,32 @@
+== AWS SES Sink Kamelet Description
+
+=== Authentication methods
+
+In this Kamelet you have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of access key/secret key or default credentials provider could be used
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+=== Required Headers
+
+In the headers, you can optionally set the following properties:
+
+- `subject` / `ce-subject` property to specify the email subject. If you do not set this property in the header, the Kamelet uses the exchange ID for the email subject.
+
+While the following headers are required
+
+- `to` / `ce-to` to provide a comma-separated list of email addresses.
+
+- `reply-to-addresses` / `ce-reply-to-addresses`to provider a comma-separated list of reply-to email addresses.
diff --git a/kamelets/aws-ses-sink.kamelet.yaml b/kamelets/aws-ses-sink.kamelet.yaml
index 6a5715a4..89c98503 100644
--- a/kamelets/aws-ses-sink.kamelet.yaml
+++ b/kamelets/aws-ses-sink.kamelet.yaml
@@ -31,21 +31,7 @@ metadata:
spec:
definition:
title: "AWS SES Sink"
- description: |-
- Send email through the Amazon Simple Email Service (SES).
-
- The basic authentication method for the SES service is to specify an access key and a secret key. These parameters are optional because the Kamelet provides a default credentials provider.
-
- If you use the default credentials provider, the SES client loads the credentials through this provider and doesn't use the basic authentication method.
-
- In the header, you can optionally set the following properties:
-
- - `subject` / `ce-subject` property to specify the email subject. If you do not set this property in the header, the Kamelet uses the exchange ID for the email subject.
-
- - `to` / `ce-to` to provide a comma-separated list of email addresses.
-
- - `reply-to-addresses` / `ce-reply-to-addresses`to provider a comma-separated list of reply-to email addresses.
-
+ description: Send email through the Amazon Simple Email Service (SES).
required:
- from
- region
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-ses-sink.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-ses-sink.kamelet.yaml
index 6a5715a4..89c98503 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-ses-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-ses-sink.kamelet.yaml
@@ -31,21 +31,7 @@ metadata:
spec:
definition:
title: "AWS SES Sink"
- description: |-
- Send email through the Amazon Simple Email Service (SES).
-
- The basic authentication method for the SES service is to specify an access key and a secret key. These parameters are optional because the Kamelet provides a default credentials provider.
-
- If you use the default credentials provider, the SES client loads the credentials through this provider and doesn't use the basic authentication method.
-
- In the header, you can optionally set the following properties:
-
- - `subject` / `ce-subject` property to specify the email subject. If you do not set this property in the header, the Kamelet uses the exchange ID for the email subject.
-
- - `to` / `ce-to` to provide a comma-separated list of email addresses.
-
- - `reply-to-addresses` / `ce-reply-to-addresses`to provider a comma-separated list of reply-to email addresses.
-
+ description: Send email through the Amazon Simple Email Service (SES).
required:
- from
- region
(camel-kamelets) 01/03: Kamelets Catalog - Make the description a one liner - AWS Secrets Manager Sink
Posted by ac...@apache.org.
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 164337a757d5ed490c867b730c49fae21c148097
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Jan 27 10:26:46 2025 +0100
Kamelets Catalog - Make the description a one liner - AWS Secrets Manager Sink
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../aws-secrets-manager-sink-description.adoc | 29 ++++++++++++++++++++++
kamelets/aws-secrets-manager-sink.kamelet.yaml | 13 +---------
.../kamelets/aws-secrets-manager-sink.kamelet.yaml | 13 +---------
3 files changed, 31 insertions(+), 24 deletions(-)
diff --git a/docs/modules/ROOT/partials/aws-secrets-manager-sink-description.adoc b/docs/modules/ROOT/partials/aws-secrets-manager-sink-description.adoc
new file mode 100644
index 00000000..d76bd40e
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-secrets-manager-sink-description.adoc
@@ -0,0 +1,29 @@
+== AWS Secrets Manager Sink Kamelet Description
+
+=== Authentication methods
+
+In this Kamelet you have the possibility of avoiding the usage of explicit static credentials by specifying the useDefaultCredentialsProvider option and set it to true.
+
+The order of evaluation for Default Credentials Provider is the following:
+
+ - Java system properties - `aws.accessKeyId` and `aws.secretKey`.
+ - Environment variables - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
+ - Web Identity Token from AWS STS.
+ - The shared credentials and config files.
+ - Amazon ECS container credentials - loaded from the Amazon ECS if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
+ - Amazon EC2 Instance profile credentials.
+
+You have also the possibility of using Profile Credentials Provider, by specifying the useProfileCredentialsProvider option to true and profileCredentialsName to the profile name.
+
+Only one of access key/secret key or default credentials provider could be used
+
+For more information about this you can look at https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials.html[AWS credentials documentation]
+
+=== Required Headers
+
+The Kamelet expects the following headers to be set:
+
+
+- `secret-name` / `ce-secret-name`: as the secret name to create.
+
+If the header won't be set the exchange ID will be used as secret name.
diff --git a/kamelets/aws-secrets-manager-sink.kamelet.yaml b/kamelets/aws-secrets-manager-sink.kamelet.yaml
index 9e4ad001..dd3748dd 100644
--- a/kamelets/aws-secrets-manager-sink.kamelet.yaml
+++ b/kamelets/aws-secrets-manager-sink.kamelet.yaml
@@ -31,18 +31,7 @@ metadata:
spec:
definition:
title: "AWS Secrets Manager Sink"
- description: |-
- Create a secret in AWS Secrets Manager.
-
- Access Key/Secret Key are the basic method for authenticating to the AWS Secrets Manager Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Secrets Manager 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:
-
- - `secret-name` / `ce-secret-name`: as the secret name to create.
-
- If the header won't be set the exchange ID will be used as secret name.
+ description: Create a secret in AWS Secrets Manager.
required:
- region
type: object
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-secrets-manager-sink.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-secrets-manager-sink.kamelet.yaml
index 9e4ad001..dd3748dd 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-secrets-manager-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-secrets-manager-sink.kamelet.yaml
@@ -31,18 +31,7 @@ metadata:
spec:
definition:
title: "AWS Secrets Manager Sink"
- description: |-
- Create a secret in AWS Secrets Manager.
-
- Access Key/Secret Key are the basic method for authenticating to the AWS Secrets Manager Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Secrets Manager 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:
-
- - `secret-name` / `ce-secret-name`: as the secret name to create.
-
- If the header won't be set the exchange ID will be used as secret name.
+ description: Create a secret in AWS Secrets Manager.
required:
- region
type: object