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 2023/03/20 10:47:35 UTC
[camel-kamelets] branch 1381-3.20.x updated (1bce479c -> d0f00dfa)
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch 1381-3.20.x
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
from 1bce479c Kafka Source Kamelets: Enable deserializeHeaders by default - Kafka SSL Source
new 570f0904 AWS DDB Sink Kamelet: Remove WriteCapacity parameter
new d0f00dfa AWS DDB Sink Kamelet: Remove WriteCapacity parameter
The 2 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:
kamelets/aws-ddb-sink.kamelet.yaml | 6 ------
.../src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml | 6 ------
2 files changed, 12 deletions(-)
[camel-kamelets] 02/02: AWS DDB Sink Kamelet: Remove WriteCapacity parameter
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch 1381-3.20.x
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit d0f00dfa56b5950273f82dbb3055711951a4f768
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Mar 20 11:42:13 2023 +0100
AWS DDB Sink Kamelet: Remove WriteCapacity parameter
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
.../src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml | 6 ------
1 file changed, 6 deletions(-)
diff --git a/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml b/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml
index 174167ae..18ffb2ee 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/aws-ddb-sink.kamelet.yaml
@@ -76,11 +76,6 @@ spec:
enum: ["PutItem", "UpdateItem", "DeleteItem"]
default: PutItem
example: PutItem
- writeCapacity:
- title: Write Capacity
- description: The provisioned throughput to reserve for writing resources to your table.
- type: integer
- default: 1
useDefaultCredentialsProvider:
title: Default Credentials Provider
description: If true, the DynamoDB client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key).
@@ -127,7 +122,6 @@ spec:
accessKey: "{{?accessKey}}"
region: "{{region}}"
operation: "{{operation}}"
- writeCapacity: "{{?writeCapacity}}"
useDefaultCredentialsProvider: "{{useDefaultCredentialsProvider}}"
uriEndpointOverride: "{{?uriEndpointOverride}}"
overrideEndpoint: "{{overrideEndpoint}}"
[camel-kamelets] 01/02: AWS DDB Sink Kamelet: Remove WriteCapacity parameter
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch 1381-3.20.x
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
commit 570f0904ad98d32c6f4d3d1351a036a6311ad7f8
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Mon Mar 20 11:41:44 2023 +0100
AWS DDB Sink Kamelet: Remove WriteCapacity parameter
Signed-off-by: Andrea Cosentino <an...@gmail.com>
---
kamelets/aws-ddb-sink.kamelet.yaml | 6 ------
1 file changed, 6 deletions(-)
diff --git a/kamelets/aws-ddb-sink.kamelet.yaml b/kamelets/aws-ddb-sink.kamelet.yaml
index 174167ae..18ffb2ee 100644
--- a/kamelets/aws-ddb-sink.kamelet.yaml
+++ b/kamelets/aws-ddb-sink.kamelet.yaml
@@ -76,11 +76,6 @@ spec:
enum: ["PutItem", "UpdateItem", "DeleteItem"]
default: PutItem
example: PutItem
- writeCapacity:
- title: Write Capacity
- description: The provisioned throughput to reserve for writing resources to your table.
- type: integer
- default: 1
useDefaultCredentialsProvider:
title: Default Credentials Provider
description: If true, the DynamoDB client loads credentials through a default credentials provider. If false, it uses the basic authentication method (access key and secret key).
@@ -127,7 +122,6 @@ spec:
accessKey: "{{?accessKey}}"
region: "{{region}}"
operation: "{{operation}}"
- writeCapacity: "{{?writeCapacity}}"
useDefaultCredentialsProvider: "{{useDefaultCredentialsProvider}}"
uriEndpointOverride: "{{?uriEndpointOverride}}"
overrideEndpoint: "{{overrideEndpoint}}"