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 devel
Looks cool, will definitely check it out!
For those who like to give support/star it: https://github.com/KaotoIO
Greets,
Raymond
On Thu, Mar 24, 2022 at 9:29 AM María Arias de Reyna
wrote:
> Hello!
>
> I would like to present you a Camel editor Rachel and I have been
> working for the past y
Thank you!
That's very nice of you.
On Thu, Mar 24, 2022 at 10:12 AM ski n wrote:
>
> Looks cool, will definitely check it out!
>
> For those who like to give support/star it: https://github.com/KaotoIO
>
> Greets,
>
> Raymond
>
>
> On Thu, Mar 24, 2022 at 9:29 AM María Arias de Reyna
> wrote:
Looks very promising!
I would like to give it a try and follow your further development.
I have a first question:
What can I do, when the backend port (8081) is already in use and I mapo
that port to 9081:
docker run --rm -d -p 9081:8081 --name kaoto-backend kaotoio/backend
How can I specify th
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 A
Hi Pasquale!
Thank you :)
Right now we don't have any cross collaboration planned with Karavan.
Although the idea is similar (visual editing of camel DSLs), the way
to implement it is completely different. But maybe we can work on the
common metadata catalog of connectors?
On Thu, Mar 24, 2022 a
To clarify, I'm recommending *clearing* the CamelSqlGeneratedKeyRows header
prior to the sql call.
On Wed, Mar 23, 2022 at 9:34 PM Reto Peter wrote:
> Hi
>
> I tried both with no success
> a) it works as normal, I get the keys back if I only run the 2nd select
> b) I set the Header before first
Can I autoscale the Camel-K-Operator deployment to have more than one
pod processing/building/runnning integrations?
