Hello, It makes totally sense from my point of view.
I will be much more easier to maintain the project basing it on kamelets where available. Thanks -- Andrea Cosentino ---------------------------------- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: [email protected] Twitter: @oscerd2 Github: oscerd On Saturday, September 18, 2021, 10:53:19 PM GMT+2, Andrea <[email protected]> wrote: Hello, finally the switch to use kamelets in Camel Kafka Connector project is in an usable state: https://github.com/apache/camel-kafka-connector/tree/kamelets this branch has refactored the existing core in reusable kamelets and has added generation of kafka connectors using the kamelet catalog as well. The generation happens using the following criteria: - one kafka connector is generated for each kamelet in the kamelet catalog. - one kafka connector is generated for each camel component ("the old way"), excluding the component used in at least one kamelet. Going forward, as the kamelet catalog will add more kamelets, I personally prefer to further reduce the number of kafka connectors generated "the old way" (most probably selecting just the most meaningful/used/that makes sense). These would made the project more maintainable by reducing number of connectors and improving their quality by reusing kamelets that are the preferred way in camel to define "connectors" and are used/will be used across all runtimes. I would like to give everyone interested some time to look at the work and think about improvements/concerns before merging it to main and shortly after releasing a new version of Camel Kafka Connector. Regards, Andrea.
