camel-git-kafka-connector sink configuration

When using camel-git-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-git-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.git.CamelGitSinkConnector

The camel-git sink connector supports 14 options, which are listed below.

Name Description Default Required Priority

camel.sink.path.localPath

Local repository path

null

true

HIGH

camel.sink.endpoint.branchName

The branch name to work on

null

false

MEDIUM

camel.sink.endpoint.password

Remote repository password

null

false

MEDIUM

camel.sink.endpoint.remoteName

The remote repository name to use in particular operation like pull

null

false

MEDIUM

camel.sink.endpoint.remotePath

The remote repository path

null

false

MEDIUM

camel.sink.endpoint.tagName

The tag name to work on

null

false

MEDIUM

camel.sink.endpoint.username

Remote repository username

null

false

MEDIUM

camel.sink.endpoint.allowEmpty

The flag to manage empty git commits

true

false

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 creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

false

MEDIUM

camel.sink.endpoint.operation

The operation to do on the repository One of: [clone] [init] [add] [remove] [commit] [commitAll] [createBranch] [deleteBranch] [createTag] [deleteTag] [status] [log] [push] [pull] [showBranches] [cherryPick] [remoteAdd] [remoteList]

null

false

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

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

false

MEDIUM

camel.component.git.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 creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

false

MEDIUM

camel.component.git.basicPropertyBinding

Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

false

LOW

The camel-git sink connector has no converters out of the box.

The camel-git sink connector has no transforms out of the box.

The camel-git sink connector has no aggregation strategies out of the box.

Back to top