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/31 13:47:03 UTC
(camel-kamelets) branch 2345-con-2 created (now 97dede4b)
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch 2345-con-2
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
at 97dede4b Kamelets Catalog - Make the description a one liner - Azure CosmosDB Sink
This branch includes the following new commits:
new 3798fa66 Kamelets Catalog - Make the description a one liner - AWS STS Assume Role Action
new a80184d4 Kamelets Catalog - Make the description a one liner - AWS Timestream Query Sink
new dcc2f1b8 Kamelets Catalog - Make the description a one liner - AWS Translate Action
new 97dede4b Kamelets Catalog - Make the description a one liner - Azure CosmosDB Sink
The 4 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.
(camel-kamelets) 04/04: Kamelets Catalog - Make the description a one liner - Azure CosmosDB Sink
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch 2345-con-2
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit 97dede4bed2bc815b7b2e324de45c751742a9bef
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Jan 31 12:06:55 2025 +0100
Kamelets Catalog - Make the description a one liner - Azure CosmosDB Sink
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../partials/azure-cosmosdb-sink-description.adoc | 23 ++++++++++++++++++++++
kamelets/azure-cosmosdb-sink.kamelet.yaml | 11 +----------
.../kamelets/azure-cosmosdb-sink.kamelet.yaml | 11 +----------
3 files changed, 25 insertions(+), 20 deletions(-)
diff --git a/docs/modules/ROOT/partials/azure-cosmosdb-sink-description.adoc b/docs/modules/ROOT/partials/azure-cosmosdb-sink-description.adoc
new file mode 100644
index 00000000..b730aa41
--- /dev/null
+++ b/docs/modules/ROOT/partials/azure-cosmosdb-sink-description.adoc
@@ -0,0 +1,23 @@
+== Azure CosmosDB Sink Kamelet Description
+
+=== Authentication methods
+
+In this Kamelet you have the possibility of using the Azure Identity mechanism or the plain Shared Account Key. Respectively the parameters are `AZURE_IDENTITY` and `SHARED_ACCOUNT_KEY`
+
+The order of evaluation for `AZURE_IDENTITY` is the following:
+
+ - Enviroment
+ - Workload Identity
+ - Managed Identity
+ - Azure Developer CLI
+ - IntelliJ
+ - Azure CLI
+ - Azure Powershell
+
+For more information about this you can look at https://learn.microsoft.com/en-us/java/api/overview/azure/identity-readme[Azure Identity documentation]
+
+=== Optional Headers
+
+In the headers, you can optionally set the `itemPartitionKey` / `ce-itemPartitionKey` property to specify the partition key for a specific item.
+
+If you do not set the property in the header, you'll need to use the static property itemPartitonKey.
diff --git a/kamelets/azure-cosmosdb-sink.kamelet.yaml b/kamelets/azure-cosmosdb-sink.kamelet.yaml
index 98ce34c3..7aa11a67 100644
--- a/kamelets/azure-cosmosdb-sink.kamelet.yaml
+++ b/kamelets/azure-cosmosdb-sink.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: "Azure CosmosDB Sink"
- description: |-
- Send Data to an Azure CosmosDB instance
-
- In the headers, you can optionally set the `itemPartitionKey` / `ce-itemPartitionKey` property to specify the partition key for a specific item.
-
- If you do not set the property in the header, you'll need to use the static property itemPartitonKey.
-
- There are two different mechanism of authentication `SHARED_ACCOUNT_KEY` and `AZURE_IDENTITY`, you could specify with credentialType property. If you're using `SHARED_ACCOUNT_KEY` accountKey property will be needed.
-
- In case of `AZURE_IDENTITY` selection, the DefaultAzureCredential will attempt to authenticate via the following mechanisms in the following order enviroment, Workload Identity, Managed Identity, Azure Developer CLI, IntelliJ, Azure CLI and Azure Powershell.
+ description: Send Data to an Azure CosmosDB instance
required:
- databaseName
- containerName
diff --git a/library/camel-kamelets/src/main/resources/kamelets/azure-cosmosdb-sink.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/azure-cosmosdb-sink.kamelet.yaml
index 98ce34c3..7aa11a67 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/azure-cosmosdb-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/azure-cosmosdb-sink.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: "Azure CosmosDB Sink"
- description: |-
- Send Data to an Azure CosmosDB instance
-
- In the headers, you can optionally set the `itemPartitionKey` / `ce-itemPartitionKey` property to specify the partition key for a specific item.
-
- If you do not set the property in the header, you'll need to use the static property itemPartitonKey.
-
- There are two different mechanism of authentication `SHARED_ACCOUNT_KEY` and `AZURE_IDENTITY`, you could specify with credentialType property. If you're using `SHARED_ACCOUNT_KEY` accountKey property will be needed.
-
- In case of `AZURE_IDENTITY` selection, the DefaultAzureCredential will attempt to authenticate via the following mechanisms in the following order enviroment, Workload Identity, Managed Identity, Azure Developer CLI, IntelliJ, Azure CLI and Azure Powershell.
+ description: Send Data to an Azure CosmosDB instance
required:
- databaseName
- containerName
(camel-kamelets) 03/04: Kamelets Catalog - Make the description a one liner - AWS Translate Action
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch 2345-con-2
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit dcc2f1b86e8c62725d7250ad9e978d9d8d7c901a
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Jan 31 10:18:12 2025 +0100
Kamelets Catalog - Make the description a one liner - AWS Translate Action
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../partials/aws-translate-action-description.adoc | 20 ++++++++++++++++++++
kamelets/aws-translate-action.kamelet.yaml | 7 +------
.../kamelets/aws-translate-action.kamelet.yaml | 7 +------
3 files changed, 22 insertions(+), 12 deletions(-)
diff --git a/docs/modules/ROOT/partials/aws-translate-action-description.adoc b/docs/modules/ROOT/partials/aws-translate-action-description.adoc
new file mode 100644
index 00000000..acf430c5
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-translate-action-description.adoc
@@ -0,0 +1,20 @@
+== AWS Translate Action 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]
diff --git a/kamelets/aws-translate-action.kamelet.yaml b/kamelets/aws-translate-action.kamelet.yaml
index 20b5fef8..bdccdab4 100644
--- a/kamelets/aws-translate-action.kamelet.yaml
+++ b/kamelets/aws-translate-action.kamelet.yaml
@@ -31,12 +31,7 @@ metadata:
spec:
definition:
title: "AWS Translate Action"
- description: |-
- Translate a text in a specific language.
-
- Access Key/Secret Key are the basic method for authenticating to the AWS Translate Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Translate 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.
+ description: Translate a text in a specific language.
required:
- region
- sourceLanguage
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-translate-action.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-translate-action.kamelet.yaml
index 20b5fef8..bdccdab4 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-translate-action.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-translate-action.kamelet.yaml
@@ -31,12 +31,7 @@ metadata:
spec:
definition:
title: "AWS Translate Action"
- description: |-
- Translate a text in a specific language.
-
- Access Key/Secret Key are the basic method for authenticating to the AWS Translate Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Translate 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.
+ description: Translate a text in a specific language.
required:
- region
- sourceLanguage
(camel-kamelets) 01/04: Kamelets Catalog - Make the description a one liner - AWS STS Assume Role Action
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch 2345-con-2
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit 3798fa6662691971ed2d3373446f94816694499c
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Jan 31 10:01:06 2025 +0100
Kamelets Catalog - Make the description a one liner - AWS STS Assume Role Action
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../aws-sts-assume-role-action-description.adoc | 27 ++++++++++++++++++++++
kamelets/aws-sts-assume-role-action.kamelet.yaml | 11 +--------
.../aws-sts-assume-role-action.kamelet.yaml | 11 +--------
3 files changed, 29 insertions(+), 20 deletions(-)
diff --git a/docs/modules/ROOT/partials/aws-sts-assume-role-action-description.adoc b/docs/modules/ROOT/partials/aws-sts-assume-role-action-description.adoc
new file mode 100644
index 00000000..8813d017
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-sts-assume-role-action-description.adoc
@@ -0,0 +1,27 @@
+== AWS STS Assume Role Action 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 this Kamelet you have to specify the following headers:
+
+- `role-arn` / `ce-role-arn` property to specify the role ARN you want to assume.
+- `role-session-name` / `ce-role-session-name` property to specify the role Session name you want to use.
diff --git a/kamelets/aws-sts-assume-role-action.kamelet.yaml b/kamelets/aws-sts-assume-role-action.kamelet.yaml
index 7648a601..72a25098 100644
--- a/kamelets/aws-sts-assume-role-action.kamelet.yaml
+++ b/kamelets/aws-sts-assume-role-action.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: "AWS STS Assume Role Action"
- description: |-
- Assume a role through STS
-
- Access Key/Secret Key are the basic method for authenticating to the AWS STS Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Translate 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.
-
- In the headers, you have to specify the `role-arn` / `ce-role-arn` property to specify the role ARN you want to assume.
-
- In the headers, you have to specify the `role-session-name` / `ce-role-session-name` property to specify the role Session name you want to use.
+ description: Assume a role through STS
required:
- region
type: object
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml
index 7648a601..72a25098 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-sts-assume-role-action.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: "AWS STS Assume Role Action"
- description: |-
- Assume a role through STS
-
- Access Key/Secret Key are the basic method for authenticating to the AWS STS Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Translate 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.
-
- In the headers, you have to specify the `role-arn` / `ce-role-arn` property to specify the role ARN you want to assume.
-
- In the headers, you have to specify the `role-session-name` / `ce-role-session-name` property to specify the role Session name you want to use.
+ description: Assume a role through STS
required:
- region
type: object
(camel-kamelets) 02/04: Kamelets Catalog - Make the description a one liner - AWS Timestream Query Sink
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch 2345-con-2
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit a80184d4ff41c6b471ecab0ede27a2aedbd57ee4
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Jan 31 10:11:51 2025 +0100
Kamelets Catalog - Make the description a one liner - AWS Timestream Query Sink
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../aws-timestream-query-sink-description.adoc | 26 ++++++++++++++++++++++
kamelets/aws-timestream-query-sink.kamelet.yaml | 11 +--------
.../aws-timestream-query-sink.kamelet.yaml | 11 +--------
3 files changed, 28 insertions(+), 20 deletions(-)
diff --git a/docs/modules/ROOT/partials/aws-timestream-query-sink-description.adoc b/docs/modules/ROOT/partials/aws-timestream-query-sink-description.adoc
new file mode 100644
index 00000000..afe5a7e0
--- /dev/null
+++ b/docs/modules/ROOT/partials/aws-timestream-query-sink-description.adoc
@@ -0,0 +1,26 @@
+== AWS Timestream Query 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 this Kamelet you have to specify the following headers:
+
+- `query` / `ce-query`: as a Timestream Query
diff --git a/kamelets/aws-timestream-query-sink.kamelet.yaml b/kamelets/aws-timestream-query-sink.kamelet.yaml
index 5859e097..b3530528 100644
--- a/kamelets/aws-timestream-query-sink.kamelet.yaml
+++ b/kamelets/aws-timestream-query-sink.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: AWS Timestream Query Sink
- description: |-
- Query an AWS Timestream Database
-
- Access Key/Secret Key are the basic method for authenticating to the AWS Timestream Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Timestream 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:
-
- - `query` / `ce-query`: as a Timestream Query
+ description: Query an AWS Timestream Database
required:
- region
type: object
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-timestream-query-sink.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-timestream-query-sink.kamelet.yaml
index 5859e097..b3530528 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-timestream-query-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-timestream-query-sink.kamelet.yaml
@@ -31,16 +31,7 @@ metadata:
spec:
definition:
title: AWS Timestream Query Sink
- description: |-
- Query an AWS Timestream Database
-
- Access Key/Secret Key are the basic method for authenticating to the AWS Timestream Service. These parameters are optional because the Kamelet provides the 'useDefaultCredentialsProvider'.
-
- When using a default Credentials Provider the Timestream 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:
-
- - `query` / `ce-query`: as a Timestream Query
+ description: Query an AWS Timestream Database
required:
- region
type: object