davsclaus opened a new issue, #3183:
URL: https://github.com/apache/camel-kamelets/issues/3183

   Today a Kafka Kamelet with a schema registry needs to know the serde 
classes, the registry properties of each vendor, and which jars to add. That is 
exactly what an integrator does not know. Instead, a Kafka Kamelet could take a 
single vendor option and configure itself from it:
   
   ```yaml
   - route:
       from:
         uri: kamelet:kafka-source
         parameters:
           topic: orders
           bootstrapServers: broker:9092
           schemaRegistry: confluent      # confluent, azure, apicurio or custom
           schemaRegistryUrl: https://registry.example.com
           schemaFormat: avro             # avro, json or protobuf
   ```
   
   ### What each vendor value would set
   
   | `schemaRegistry` | Sets up |
   |---|---|
   | `confluent` | The Confluent serde classes for the format, 
`schema.registry.url`, and the registry login (basic auth or an API key) |
   | `azure` | The Azure Schema Registry serde classes, the schema group, and 
the Azure credential |
   | `apicurio` | The Apicurio serde classes, `apicurio.registry.url`, and the 
optional Keycloak login |
   | `custom` | Nothing: the user gives the serde classes and the properties |
   | not set | No registry, as today |
   
   ### Open points
   
   - **Templates have no conditions.** A Kamelet template cannot pick serde 
classes from an option value. Ways to do it:
     - a nested property placeholder per vendor and format;
     - hidden default properties;
     - support in the camel-kafka component itself, for example a 
`schemaRegistryVendor` option that knows the serde classes. That last one would 
also help Kafka routes that do not use a Kamelet.
   - **Dependencies.** Each vendor needs its own serde jars. A Kamelet lists 
its dependencies statically, so either every vendor's jars come with every 
Kafka user, or the dependencies come from the vendor choice, which needs 
runtime support.
   - **Licenses.** Kamelet dependencies must have an Apache-compatible license. 
Check the Confluent and Azure serde artifacts.
   - **Relation to other issues.** This would replace the per-vendor Kamelets: 
the seven Apicurio Kamelets (#3182), and the Azure Schema Registry Kamelets 
removed in #3165. It is also the registry part of the Kafka consolidation in 
#3144.
   
   _Claude Code on behalf of Claus Ibsen_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to