camel-docker-kafka-connector sink configuration
Connector Description: Manage Docker containers.
When using camel-docker-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-docker-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>
To use this sink connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.docker.CamelDockerSinkConnector
The camel-docker sink connector supports 39 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Required Which operation to use One of: [events] [stats] [auth] [info] [ping] [version] [imagebuild] [imagecreate] [imageinspect] [imagelist] [imagepull] [imagepushimageremove] [imagesearch] [imagetag] [containerattach] [containercommit] [containercopyfile] [containercreate] [containerdiffinspectcontainer] [containerkill] [containerlist] [containerlog] [containerpause] [containerrestart] [containerremove] [containerstartcontainerstop] [containertop] [containerunpause] [containerwait] [execcreate] [execstart]. Enum values:
|
HIGH |
||
Email address associated with the user. |
MEDIUM |
||
Required Docker host. |
"localhost" |
HIGH |
|
Docker port. |
"2375" |
MEDIUM |
|
Request timeout for response (in seconds). |
MEDIUM |
||
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 creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
MEDIUM |
|
The fully qualified class name of the DockerCmdExecFactory implementation to use. |
"com.github.dockerjava.netty.NettyDockerCmdExecFactory" |
MEDIUM |
|
Whether to follow redirect filter. |
false |
MEDIUM |
|
Whether to use logging filter. |
false |
MEDIUM |
|
Maximum route connections. |
"100" |
MEDIUM |
|
Maximum total connections. |
"100" |
MEDIUM |
|
Additional configuration parameters as key/value pairs. |
MEDIUM |
||
Server address for docker registry. |
"https://index.docker.io/v1/" |
MEDIUM |
|
Socket connection mode. |
true |
MEDIUM |
|
Location containing the SSL certificate chain. |
MEDIUM |
||
Password to authenticate with. |
MEDIUM |
||
Use HTTPS communication. |
false |
MEDIUM |
|
Check TLS. |
false |
MEDIUM |
|
User name to authenticate with. |
MEDIUM |
||
To use the shared docker configuration. |
MEDIUM |
||
Email address associated with the user. |
MEDIUM |
||
Required Docker host. |
"localhost" |
HIGH |
|
Docker port. |
"2375" |
MEDIUM |
|
Request timeout for response (in seconds). |
MEDIUM |
||
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 creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
MEDIUM |
|
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
MEDIUM |
|
The fully qualified class name of the DockerCmdExecFactory implementation to use. |
"com.github.dockerjava.netty.NettyDockerCmdExecFactory" |
MEDIUM |
|
Whether to follow redirect filter. |
false |
MEDIUM |
|
Whether to use logging filter. |
false |
MEDIUM |
|
Maximum route connections. |
"100" |
MEDIUM |
|
Maximum total connections. |
"100" |
MEDIUM |
|
Additional configuration parameters as key/value pairs. |
MEDIUM |
||
Server address for docker registry. |
"https://index.docker.io/v1/" |
MEDIUM |
|
Socket connection mode. |
true |
MEDIUM |
|
Location containing the SSL certificate chain. |
MEDIUM |
||
Password to authenticate with. |
MEDIUM |
||
Use HTTPS communication. |
false |
MEDIUM |
|
Check TLS. |
false |
MEDIUM |
|
User name to authenticate with. |
MEDIUM |
The camel-docker sink connector has no converters out of the box.
The camel-docker sink connector has no transforms out of the box.
The camel-docker sink connector has no aggregation strategies out of the box.