camel-google-calendar-kafka-connector sink configuration

Connector Description: Perform various operations on a Google Calendar.

When using camel-google-calendar-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-google-calendar-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.googlecalendar.CamelGooglecalendarSinkConnector

The camel-google-calendar sink connector supports 26 options, which are listed below.

Name Description Default Priority

camel.sink.path.apiName

Required What kind of operation to perform One of: [ACL] [LIST] [CALENDARS] [CHANNELS] [COLORS] [FREEBUSY] [EVENTS] [SETTINGS].

Enum values:

  • ACL

  • LIST

  • CALENDARS

  • CHANNELS

  • COLORS

  • FREEBUSY

  • EVENTS

  • SETTINGS

HIGH

camel.sink.path.methodName

Required What sub operation to use for the selected operation One of: [calendarImport] [clear] [delete] [get] [insert] [instances] [list] [move] [patch] [query] [quickAdd] [stop] [update] [watch].

Enum values:

  • calendarImport

  • clear

  • delete

  • get

  • insert

  • instances

  • list

  • move

  • patch

  • query

  • quickAdd

  • stop

  • update

  • watch

HIGH

camel.sink.endpoint.applicationName

Google calendar application name. Example would be camel-google-calendar/1.0.

MEDIUM

camel.sink.endpoint.clientId

Client ID of the calendar application.

MEDIUM

camel.sink.endpoint.inBody

Sets the name of a parameter to be passed in the exchange In Body.

MEDIUM

camel.sink.endpoint.scopes

Specifies the level of permissions you want a calendar application to have to a user account. You can separate multiple scopes by comma. See https://developers.google.com/google-apps/calendar/auth for more info.

"https://www.googleapis.com/auth/calendar"

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

MEDIUM

camel.sink.endpoint.accessToken

OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.

MEDIUM

camel.sink.endpoint.clientSecret

Client secret of the calendar application.

MEDIUM

camel.sink.endpoint.emailAddress

The emailAddress of the Google Service Account.

MEDIUM

camel.sink.endpoint.p12FileName

The name of the p12 file which has the private key to use with the Google Service Account.

MEDIUM

camel.sink.endpoint.refreshToken

OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.

MEDIUM

camel.sink.endpoint.user

The email address of the user the application is trying to impersonate in the service account flow.

MEDIUM

camel.component.google-calendar.applicationName

Google calendar application name. Example would be camel-google-calendar/1.0.

MEDIUM

camel.component.google-calendar.clientId

Client ID of the calendar application.

MEDIUM

camel.component.google-calendar.configuration

To use the shared configuration.

MEDIUM

camel.component.google-calendar.scopes

Specifies the level of permissions you want a calendar application to have to a user account. You can separate multiple scopes by comma. See https://developers.google.com/google-apps/calendar/auth for more info.

"https://www.googleapis.com/auth/calendar"

MEDIUM

camel.component.google-calendar.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

MEDIUM

camel.component.google-calendar.autowiredEnabled

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

camel.component.google-calendar.clientFactory

To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleCalendarClientFactory.

MEDIUM

camel.component.google-calendar.accessToken

OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.

MEDIUM

camel.component.google-calendar.clientSecret

Client secret of the calendar application.

MEDIUM

camel.component.google-calendar.emailAddress

The emailAddress of the Google Service Account.

MEDIUM

camel.component.google-calendar.p12FileName

The name of the p12 file which has the private key to use with the Google Service Account.

MEDIUM

camel.component.google-calendar.refreshToken

OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.

MEDIUM

camel.component.google-calendar.user

The email address of the user the application is trying to impersonate in the service account flow.

MEDIUM

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

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

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

Back to top