Thanks Maria and Rachel, excellent stuff! I wonder if you've already explored some cross collaboration with Camel Karavan [1]. It looks to me that there are certain areas covered by both tools.
Regards, Pasquale. [1] https://github.com/apache/camel-karavan On Thu, Mar 24, 2022 at 9:29 AM María Arias de Reyna <dela...@apache.org> wrote: > Hello! > > I would like to present you a Camel editor Rachel and I have been > working for the past year: Kaoto. > > Kaoto is an acronym for **Ka**mel **O**rchestration **To**ol. > > Kaoto has a source code editor and a drag and drop graphical space > that are synchronized with each other. > > We started the development focused on Kamelet Bindings, but we soon > realized we could add more DSLs and we are close to have Kamelet and > Camel Route support too. Each Kaoto instance has a list of remote urls > from which to build the catalog of steps or building blocks. We > started a metadata catalog, like the one for Kamelets, to describe > camel connectors to be able to use them also easily in our graphical > editor[1]. This half-done catalog of metadata allows us to add camel > connectors to our integrations. This is an experiment and we would > welcome input on how to make it better, specially if it can be reused > for other purposes. > > The user interface is extendable too[2]. With this configuration each > step can have its own microfrontend[3] to configure its properties. > This is not only useful when you add your own steps, but it can also > help you adapt Kaoto to different kinds of users, hiding or extending > certain details important for each use-case. > > The idea behind all these catalogs of configuration is not to use git > repositories in production, but to have some configuration that can be > reloaded/refreshed live. Right now we also support zip/jar files with > the configuration, both for the step catalog and the view definitions > catalog. We may want to extend to use some other types of cache, more > k-native style, for when not used as standalone. > > We are also working on one-click support for cloud-native Apache Camel > deployments via Camel-K. That's not yet enabled, partly because we > want it to be tied to some form of authentication to allow users to > have their own configuration and deployments. > > More information on our webpage: https://kaoto.io/about/ > > You can quickly test it via docker: https://kaoto.io/quickstart/ Make > sure your docker images have access to internet to be able to access > the kamelet catalogs! > > [1] https://github.com/apache/camel-kamelets > [2] https://github.com/KaotoIO/kaoto-viewdefinition-catalog > [3] https://martinfowler.com/articles/micro-frontends.html >
