Kafka Not Secured with Apicurio Registry secured with Keycloak Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Send data to Kafka topics on an insecure broker with Apicurio Registry secured with Keycloak.
The Kamelet is able to understand the following headers to be set:
-
key
/ce-key
: as message key -
partition-key
/ce-partitionkey
: as message partition key
Both the headers are optional.
Configuration Options
The following table summarizes the configuration options available for the kafka-not-secured-apicurio-registry-sink
Kamelet:
Property | Name | Description | Type | Default | Example |
---|---|---|---|---|---|
Apicurio Registry Auth Client ID | Required The Client ID in Keycloak instance securing the Apicurio Registry. | string | |||
Apicurio Registry Auth Client Secret | Required The Client Secret in Keycloak instance securing the Apicurio Registry. | string | |||
Apicurio Registry Auth Password | Required The Password in Keycloak instance securing the Apicurio Registry. | string | |||
Apicurio Registry Auth Realm | Required The Realm in Keycloak instance securing the Apicurio Registry. | string | |||
Apicurio Registry Auth Service URL | Required The URL for Keycloak instance securing the Apicurio Registry. | string | http://my-keycloak.com:8080/ | ||
Apicurio Registry Auth Username | Required The Username in Keycloak instance securing the Apicurio Registry. | string | |||
Apicurio Registry URL | Required The Apicurio Schema Registry URL. | string | |||
Bootstrap Servers | Required Comma separated list of Kafka Broker URLs. | string | |||
Topic Names | Required Comma separated list of Kafka topic names. | string | |||
Avro Datum Provider | How to write data with Avro. | string | io.apicurio.registry.serde.avro.ReflectAvroDatumProvider | ||
Value Serializer | Serliazer class for value that implements the Serializer interface. | string | io.apicurio.registry.serde.avro.AvroKafkaSerializer |
Dependencies
At runtime, the kafka-not-secured-apicurio-registry-sink
Kamelet relies upon the presence of the following dependencies:
-
camel:core
-
camel:kamelet
-
camel:kafka
-
mvn:io.apicurio:apicurio-registry-serdes-avro-serde:2.4.14.Final
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camel
Supposing you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:timer-source"
parameters:
period: 10000
message: 'test'
steps:
- to:
uri: "kamelet:kafka-not-secured-apicurio-registry-sink"
You can now run it directly through the following command
camel run route.yaml