This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch cutting-down-connectors in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git
commit 32c16a012e0e6c8ba8679d59aab97f25a09958f6 Author: Andrea Cosentino <[email protected]> AuthorDate: Thu Aug 6 19:36:49 2020 +0200 Removed old docs for removed connectors --- .../camel-aws-ec2-kafka-sink-connector.adoc | 49 --------------------- .../camel-aws-ecs-kafka-sink-connector.adoc | 49 --------------------- .../camel-aws-eks-kafka-sink-connector.adoc | 49 --------------------- .../camel-aws-iam-kafka-sink-connector.adoc | 49 --------------------- .../camel-aws-kms-kafka-sink-connector.adoc | 49 --------------------- .../camel-aws-mq-kafka-sink-connector.adoc | 49 --------------------- .../camel-aws-msk-kafka-sink-connector.adoc | 49 --------------------- .../camel-aws2-ec2-kafka-sink-connector.adoc | 51 ---------------------- .../camel-aws2-ecs-kafka-sink-connector.adoc | 51 ---------------------- .../camel-aws2-eks-kafka-sink-connector.adoc | 51 ---------------------- .../camel-aws2-iam-kafka-sink-connector.adoc | 51 ---------------------- .../camel-aws2-kms-kafka-sink-connector.adoc | 51 ---------------------- .../camel-aws2-mq-kafka-sink-connector.adoc | 51 ---------------------- .../camel-aws2-msk-kafka-sink-connector.adoc | 51 ---------------------- 14 files changed, 700 deletions(-) diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-ec2-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-ec2-kafka-sink-connector.adoc deleted file mode 100644 index 6e0f06f..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws-ec2-kafka-sink-connector.adoc +++ /dev/null @@ -1,49 +0,0 @@ -// kafka-connector options: START -[[camel-aws-ec2-kafka-connector-sink]] -= camel-aws-ec2-kafka-connector sink configuration - -When using camel-aws-ec2-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws-ec2-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws-ec2 sink connector supports 23 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | null | HIGH -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EC2 client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EC2 client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws-ec2.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws-ec2.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | MEDIUM -| *camel.component.aws-ec2.configuration* | The component configuration | null | MEDIUM -| *camel.component.aws-ec2.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws-ec2.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | [...] -| *camel.component.aws-ec2.proxyHost* | To define a proxy host when instantiating the EC2 client | null | MEDIUM -| *camel.component.aws-ec2.proxyPort* | To define a proxy port when instantiating the EC2 client | null | MEDIUM -| *camel.component.aws-ec2.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws-ec2.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws-ec2.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws-ec2.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-ecs-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-ecs-kafka-sink-connector.adoc deleted file mode 100644 index c543de6..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws-ecs-kafka-sink-connector.adoc +++ /dev/null @@ -1,49 +0,0 @@ -// kafka-connector options: START -[[camel-aws-ecs-kafka-connector-sink]] -= camel-aws-ecs-kafka-connector sink configuration - -When using camel-aws-ecs-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws-ecs-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws-ecs sink connector supports 23 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.ecsClient* | To use a existing configured AWS ECS as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the ECS client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the ECS client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws-ecs.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws-ecs.configuration* | The component configuration | null | MEDIUM -| *camel.component.aws-ecs.ecsClient* | To use a existing configured AWS ECS as client | null | MEDIUM -| *camel.component.aws-ecs.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws-ecs.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.component.aws-ecs.proxyHost* | To define a proxy host when instantiating the ECS client | null | MEDIUM -| *camel.component.aws-ecs.proxyPort* | To define a proxy port when instantiating the ECS client | null | MEDIUM -| *camel.component.aws-ecs.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws-ecs.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.component.aws-ecs.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws-ecs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-eks-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-eks-kafka-sink-connector.adoc deleted file mode 100644 index 856a427..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws-eks-kafka-sink-connector.adoc +++ /dev/null @@ -1,49 +0,0 @@ -// kafka-connector options: START -[[camel-aws-eks-kafka-connector-sink]] -= camel-aws-eks-kafka-connector sink configuration - -When using camel-aws-eks-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws-eks-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws-eks sink connector supports 23 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.eksClient* | To use a existing configured AWS EKS as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EKS client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EKS client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws-eks.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws-eks.configuration* | The component configuration | null | MEDIUM -| *camel.component.aws-eks.eksClient* | To use a existing configured AWS EKS as client | null | MEDIUM -| *camel.component.aws-eks.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws-eks.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.component.aws-eks.proxyHost* | To define a proxy host when instantiating the EKS client | null | MEDIUM -| *camel.component.aws-eks.proxyPort* | To define a proxy port when instantiating the EKS client | null | MEDIUM -| *camel.component.aws-eks.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws-eks.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.component.aws-eks.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws-eks.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-iam-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-iam-kafka-sink-connector.adoc deleted file mode 100644 index dce365b..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws-iam-kafka-sink-connector.adoc +++ /dev/null @@ -1,49 +0,0 @@ -// kafka-connector options: START -[[camel-aws-iam-kafka-connector-sink]] -= camel-aws-iam-kafka-connector sink configuration - -When using camel-aws-iam-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws-iam-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws-iam sink connector supports 23 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.iamClient* | To use a existing configured AWS IAM as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | HIGH -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the IAM client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the IAM client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws-iam.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws-iam.configuration* | The component configuration | null | MEDIUM -| *camel.component.aws-iam.iamClient* | To use a existing configured AWS IAM as client | null | MEDIUM -| *camel.component.aws-iam.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws-iam.operation* | The operation to perform One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | HIGH -| *camel.component.aws-iam.proxyHost* | To define a proxy host when instantiating the IAM client | null | MEDIUM -| *camel.component.aws-iam.proxyPort* | To define a proxy port when instantiating the IAM client | null | MEDIUM -| *camel.component.aws-iam.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws-iam.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.component.aws-iam.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws-iam.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-kms-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-kms-kafka-sink-connector.adoc deleted file mode 100644 index fec48a9..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws-kms-kafka-sink-connector.adoc +++ /dev/null @@ -1,49 +0,0 @@ -// kafka-connector options: START -[[camel-aws-kms-kafka-connector-sink]] -= camel-aws-kms-kafka-connector sink configuration - -When using camel-aws-kms-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws-kms-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws-kms sink connector supports 23 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.kmsClient* | To use a existing configured AWS KMS as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | HIGH -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the KMS client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the KMS client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which KMS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws-kms.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws-kms.configuration* | The Component configuration | null | MEDIUM -| *camel.component.aws-kms.kmsClient* | To use a existing configured AWS KMS as client | null | MEDIUM -| *camel.component.aws-kms.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws-kms.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | HIGH -| *camel.component.aws-kms.proxyHost* | To define a proxy host when instantiating the KMS client | null | MEDIUM -| *camel.component.aws-kms.proxyPort* | To define a proxy port when instantiating the KMS client | null | MEDIUM -| *camel.component.aws-kms.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws-kms.region* | The region in which KMS client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.component.aws-kms.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws-kms.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-mq-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-mq-kafka-sink-connector.adoc deleted file mode 100644 index 36b7ef1..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws-mq-kafka-sink-connector.adoc +++ /dev/null @@ -1,49 +0,0 @@ -// kafka-connector options: START -[[camel-aws-mq-kafka-connector-sink]] -= camel-aws-mq-kafka-connector sink configuration - -When using camel-aws-mq-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws-mq-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws-mq sink connector supports 23 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | HIGH -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MQ client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MQ client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws-mq.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws-mq.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | MEDIUM -| *camel.component.aws-mq.configuration* | The Component configuration | null | MEDIUM -| *camel.component.aws-mq.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws-mq.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | HIGH -| *camel.component.aws-mq.proxyHost* | To define a proxy host when instantiating the MQ client | null | MEDIUM -| *camel.component.aws-mq.proxyPort* | To define a proxy port when instantiating the MQ client | null | MEDIUM -| *camel.component.aws-mq.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws-mq.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.component.aws-mq.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws-mq.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws-msk-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws-msk-kafka-sink-connector.adoc deleted file mode 100644 index d8c7754..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws-msk-kafka-sink-connector.adoc +++ /dev/null @@ -1,49 +0,0 @@ -// kafka-connector options: START -[[camel-aws-msk-kafka-connector-sink]] -= camel-aws-msk-kafka-connector sink configuration - -When using camel-aws-msk-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws-msk-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws-msk sink connector supports 23 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.mskClient* | To use a existing configured AWS MSK as client | null | MEDIUM -| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | HIGH -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MSK client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MSK client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws-msk.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws-msk.configuration* | The component configuration | null | MEDIUM -| *camel.component.aws-msk.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws-msk.mskClient* | To use a existing configured AWS MSK as client | null | MEDIUM -| *camel.component.aws-msk.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | HIGH -| *camel.component.aws-msk.proxyHost* | To define a proxy host when instantiating the MSK client | null | MEDIUM -| *camel.component.aws-msk.proxyPort* | To define a proxy port when instantiating the MSK client | null | MEDIUM -| *camel.component.aws-msk.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws-msk.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the capitalized name of the region (for example AP_EAST_1) You'll need to use the name Regions.EU_WEST_1.name() | null | MEDIUM -| *camel.component.aws-msk.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws-msk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-ec2-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-ec2-kafka-sink-connector.adoc deleted file mode 100644 index 6cce97f..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws2-ec2-kafka-sink-connector.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// kafka-connector options: START -[[camel-aws2-ec2-kafka-connector-sink]] -= camel-aws2-ec2-kafka-connector sink configuration - -When using camel-aws2-ec2-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws2-ec2-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws2-ec2 sink connector supports 25 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | null | HIGH -| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EC2 client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EC2 client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which EC2 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.component.aws2-ec2.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws2-ec2.amazonEc2Client* | To use a existing configured AmazonEC2Client as client | null | MEDIUM -| *camel.component.aws2-ec2.configuration* | The component configuration | null | MEDIUM -| *camel.component.aws2-ec2.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...] -| *camel.component.aws2-ec2.operation* | The operation to perform. It can be createAndRunInstances, startInstances, stopInstances, terminateInstances, describeInstances, describeInstancesStatus, rebootInstances, monitorInstances, unmonitorInstances, createTags or deleteTags One of: [createAndRunInstances] [startInstances] [stopInstances] [terminateInstances] [describeInstances] [describeInstancesStatus] [rebootInstances] [monitorInstances] [unmonitorInstances] [createTags] [deleteTags] | [...] -| *camel.component.aws2-ec2.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.component.aws2-ec2.proxyHost* | To define a proxy host when instantiating the EC2 client | null | MEDIUM -| *camel.component.aws2-ec2.proxyPort* | To define a proxy port when instantiating the EC2 client | null | MEDIUM -| *camel.component.aws2-ec2.proxyProtocol* | To define a proxy protocol when instantiating the EC2 client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws2-ec2.region* | The region in which EC2 client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws2-ec2.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws2-ec2.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-ecs-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-ecs-kafka-sink-connector.adoc deleted file mode 100644 index 37cc657..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws2-ecs-kafka-sink-connector.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// kafka-connector options: START -[[camel-aws2-ecs-kafka-connector-sink]] -= camel-aws2-ecs-kafka-connector sink configuration - -When using camel-aws2-ecs-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws2-ecs-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws2-ecs sink connector supports 25 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.ecsClient* | To use a existing configured AWS ECS as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the ECS client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the ECS client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws2-ecs.configuration* | Component configuration | null | MEDIUM -| *camel.component.aws2-ecs.ecsClient* | To use a existing configured AWS ECS as client | null | MEDIUM -| *camel.component.aws2-ecs.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...] -| *camel.component.aws2-ecs.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.component.aws2-ecs.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.component.aws2-ecs.proxyHost* | To define a proxy host when instantiating the ECS client | null | MEDIUM -| *camel.component.aws2-ecs.proxyPort* | To define a proxy port when instantiating the ECS client | null | MEDIUM -| *camel.component.aws2-ecs.proxyProtocol* | To define a proxy protocol when instantiating the ECS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws2-ecs.region* | The region in which ECS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws2-ecs.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.component.aws2-ecs.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws2-ecs.secretKey* | Amazon AWS Secret Key | null | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-eks-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-eks-kafka-sink-connector.adoc deleted file mode 100644 index ca1cd64..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws2-eks-kafka-sink-connector.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// kafka-connector options: START -[[camel-aws2-eks-kafka-connector-sink]] -= camel-aws2-eks-kafka-connector sink configuration - -When using camel-aws2-eks-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws2-eks-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws2-eks sink connector supports 25 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.eksClient* | To use a existing configured AWS EKS as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the EKS client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the EKS client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws2-eks.configuration* | Component configuration | null | MEDIUM -| *camel.component.aws2-eks.eksClient* | To use a existing configured AWS EKS as client | null | MEDIUM -| *camel.component.aws2-eks.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...] -| *camel.component.aws2-eks.operation* | The operation to perform One of: [listClusters] [describeCluster] [createCluster] [deleteCluster] | null | HIGH -| *camel.component.aws2-eks.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.component.aws2-eks.proxyHost* | To define a proxy host when instantiating the EKS client | null | MEDIUM -| *camel.component.aws2-eks.proxyPort* | To define a proxy port when instantiating the EKS client | null | MEDIUM -| *camel.component.aws2-eks.proxyProtocol* | To define a proxy protocol when instantiating the EKS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws2-eks.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws2-eks.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.component.aws2-eks.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws2-eks.secretKey* | Amazon AWS Secret Key | null | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-iam-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-iam-kafka-sink-connector.adoc deleted file mode 100644 index 61eb679..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws2-iam-kafka-sink-connector.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// kafka-connector options: START -[[camel-aws2-iam-kafka-connector-sink]] -= camel-aws2-iam-kafka-connector sink configuration - -When using camel-aws2-iam-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws2-iam-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws2-iam sink connector supports 25 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.iamClient* | To use a existing configured AWS IAM as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | HIGH -| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the IAM client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the IAM client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws2-iam.configuration* | Component configuration | null | MEDIUM -| *camel.component.aws2-iam.iamClient* | To use a existing configured AWS IAM as client | null | MEDIUM -| *camel.component.aws2-iam.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...] -| *camel.component.aws2-iam.operation* | The operation to perform One of: [listAccessKeys] [createUser] [deleteUser] [getUser] [listUsers] [createAccessKey] [deleteAccessKey] [updateAccessKey] [createGroup] [deleteGroup] [listGroups] [addUserToGroup] [removeUserFromGroup] | null | HIGH -| *camel.component.aws2-iam.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.component.aws2-iam.proxyHost* | To define a proxy host when instantiating the IAM client | null | MEDIUM -| *camel.component.aws2-iam.proxyPort* | To define a proxy port when instantiating the IAM client | null | MEDIUM -| *camel.component.aws2-iam.proxyProtocol* | To define a proxy protocol when instantiating the IAM client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws2-iam.region* | The region in which IAM client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws2-iam.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.component.aws2-iam.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws2-iam.secretKey* | Amazon AWS Secret Key | null | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-kms-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-kms-kafka-sink-connector.adoc deleted file mode 100644 index 7fe15c9..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws2-kms-kafka-sink-connector.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// kafka-connector options: START -[[camel-aws2-kms-kafka-connector-sink]] -= camel-aws2-kms-kafka-connector sink configuration - -When using camel-aws2-kms-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws2-kms-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws2-kms sink connector supports 25 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.kmsClient* | To use a existing configured AWS KMS as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | HIGH -| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the KMS client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the KMS client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws2-kms.configuration* | Component configuration | null | MEDIUM -| *camel.component.aws2-kms.kmsClient* | To use a existing configured AWS KMS as client | null | MEDIUM -| *camel.component.aws2-kms.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...] -| *camel.component.aws2-kms.operation* | The operation to perform One of: [listKeys] [createKey] [disableKey] [scheduleKeyDeletion] [describeKey] [enableKey] | null | HIGH -| *camel.component.aws2-kms.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.component.aws2-kms.proxyHost* | To define a proxy host when instantiating the KMS client | null | MEDIUM -| *camel.component.aws2-kms.proxyPort* | To define a proxy port when instantiating the KMS client | null | MEDIUM -| *camel.component.aws2-kms.proxyProtocol* | To define a proxy protocol when instantiating the KMS client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws2-kms.region* | The region in which EKS client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws2-kms.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.component.aws2-kms.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws2-kms.secretKey* | Amazon AWS Secret Key | null | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-mq-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-mq-kafka-sink-connector.adoc deleted file mode 100644 index 1f3a108..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws2-mq-kafka-sink-connector.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// kafka-connector options: START -[[camel-aws2-mq-kafka-connector-sink]] -= camel-aws2-mq-kafka-connector sink configuration - -When using camel-aws2-mq-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws2-mq-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws2-mq sink connector supports 25 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | MEDIUM -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | HIGH -| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MQ client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MQ client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws2-mq.amazonMqClient* | To use a existing configured AmazonMQClient as client | null | MEDIUM -| *camel.component.aws2-mq.configuration* | Component configuration | null | MEDIUM -| *camel.component.aws2-mq.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.aws2-mq.operation* | The operation to perform. It can be listBrokers,createBroker,deleteBroker One of: [listBrokers] [createBroker] [deleteBroker] [rebootBroker] [updateBroker] [describeBroker] | null | HIGH -| *camel.component.aws2-mq.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.component.aws2-mq.proxyHost* | To define a proxy host when instantiating the MQ client | null | MEDIUM -| *camel.component.aws2-mq.proxyPort* | To define a proxy port when instantiating the MQ client | null | MEDIUM -| *camel.component.aws2-mq.proxyProtocol* | To define a proxy protocol when instantiating the MQ client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws2-mq.region* | The region in which MQ client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws2-mq.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.component.aws2-mq.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws2-mq.secretKey* | Amazon AWS Secret Key | null | MEDIUM -|=== -// kafka-connector options: END diff --git a/docs/modules/ROOT/pages/connectors/camel-aws2-msk-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-aws2-msk-kafka-sink-connector.adoc deleted file mode 100644 index c73f440..0000000 --- a/docs/modules/ROOT/pages/connectors/camel-aws2-msk-kafka-sink-connector.adoc +++ /dev/null @@ -1,51 +0,0 @@ -// kafka-connector options: START -[[camel-aws2-msk-kafka-connector-sink]] -= camel-aws2-msk-kafka-connector sink configuration - -When using camel-aws2-msk-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector: - -[source,xml] ----- -<dependency> - <groupId>org.apache.camel.kafkaconnector</groupId> - <artifactId>camel-aws2-msk-kafka-connector</artifactId> - <version>x.x.x</version> - <!-- use the same version as your Camel Kafka connector version --> -</dependency> ----- - - -The camel-aws2-msk sink connector supports 25 options, which are listed below. - - - -[width="100%",cols="2,5,^1,2",options="header"] -|=== -| Name | Description | Default | Priority -| *camel.sink.path.label* | Logical name | null | HIGH -| *camel.sink.endpoint.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then cre [...] -| *camel.sink.endpoint.mskClient* | To use a existing configured AWS MSK as client | null | MEDIUM -| *camel.sink.endpoint.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | HIGH -| *camel.sink.endpoint.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.sink.endpoint.proxyHost* | To define a proxy host when instantiating the MSK client | null | MEDIUM -| *camel.sink.endpoint.proxyPort* | To define a proxy port when instantiating the MSK client | null | MEDIUM -| *camel.sink.endpoint.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.sink.endpoint.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.sink.endpoint.basicPropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | MEDIUM -| *camel.sink.endpoint.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.sink.endpoint.secretKey* | Amazon AWS Secret Key | null | MEDIUM -| *camel.component.aws2-msk.configuration* | Component configuration | null | MEDIUM -| *camel.component.aws2-msk.lazyStartProducer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed the [...] -| *camel.component.aws2-msk.mskClient* | To use a existing configured AWS MSK as client | null | MEDIUM -| *camel.component.aws2-msk.operation* | The operation to perform One of: [listClusters] [createCluster] [deleteCluster] [describeCluster] | null | HIGH -| *camel.component.aws2-msk.pojoRequest* | If we want to use a POJO request as body or not | false | MEDIUM -| *camel.component.aws2-msk.proxyHost* | To define a proxy host when instantiating the MSK client | null | MEDIUM -| *camel.component.aws2-msk.proxyPort* | To define a proxy port when instantiating the MSK client | null | MEDIUM -| *camel.component.aws2-msk.proxyProtocol* | To define a proxy protocol when instantiating the MSK client One of: [HTTP] [HTTPS] | "HTTPS" | MEDIUM -| *camel.component.aws2-msk.region* | The region in which MSK client needs to work. When using this parameter, the configuration will expect the lowercase name of the region (for example ap-east-1) You'll need to use the name Region.EU_WEST_1.id() | null | MEDIUM -| *camel.component.aws2-msk.basicPropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | MEDIUM -| *camel.component.aws2-msk.accessKey* | Amazon AWS Access Key | null | MEDIUM -| *camel.component.aws2-msk.secretKey* | Amazon AWS Secret Key | null | MEDIUM -|=== -// kafka-connector options: END
