apache / camel-karavan Goto Github PK

View Code? Open in Web Editor NEW

396.0 34.0 133.0 33.24 MB

Apache Camel Karavan a Low-code Data Integration Platform

Home Page: https://camel.apache.org

License: Apache License 2.0

Java 8.29% HTML 0.07% TypeScript 87.36% CSS 3.96% JavaScript 0.10% Shell 0.14% Dockerfile 0.08%

camel integration java docker kubernetes low-code vscode

camel-karavan's Introduction

Apache Camel Karavan

Apache Camel Karavan is a Low-Code Data Integration Platform It simplifies the Apache Camel experience and accelerates developer performance by visually designing and rapidly deploying integration microservices.

Full power of Apache Camel through Visual Tool
From Low-code use-cases to Pro-code projects
Powered by 10+ years of Community Intelligence

Features

Designer

Enterprise Integration Patterns
300+ Integration Components
REST API designer with OpenAPI to REST DSL generator
YAML for Integration and Java custom code

Topology view

Route designer

REST API designer

Deployer

Simple shell scripts for build and deploy
Configuration
Predefined customizable scripts for different platforms

Developer Dashboard

Hot Reload
View live logs during development
Tracing Exchange Data

Architecture

Apache Camel Karavan components:

Karavan app acts as the central interface for the platform, allowing users to manage and orchestrate their integration projects.
Build Container started by the Karavan app to run integrations in developer mode (dev-mode), package and deploy integrations.
Integration microservices delivered by the platform.
Git repository stores all essential project files, including integration YAML configurations, application.properties, container configurations, deployment resources, and templates. It is considered the source of truth for the applications.
An Image Registry is used by the Apache Camel Karavan to store container images that are generated during the build process.

Local

Karavan provides VS Code extension for local developer experience

Design, code and run integrations on your laptop or PC
Deploy to Kubernetes or Openshift
Download from Marketplace or Open VSX Registry

Documentation

How to install on

Developer guide

How to build

Feedback

If you haven't done so yet, please be sure to download Karavan and give it a try. We're excited to receive your feedback and learn about your experiences!

camel-karavan's People

Contributors

Stargazers

Watchers

Forkers

mgubaidullin isabella232 carlosthe19916 croway nicolaferraro mujidd 0xhexe eliefrancis1 apupier d3vel0per sonatype-lift-apache toonalbers rafamqrs tom-sapletta-com kinggreatwarrior ccitacc siu-fung fendaq dw3105 cristph joshiraez curryzxh ghostdaxia suqcnn ztt820 grandhidileep jeannyil-camel-playground bethune 00xe8 guoxunbo suoxun victorfim wangtengteng iwen-git bhangun wzlalala ananh5 markingit maxandersen nicholasc69 sureshchandra999 rrbanda zhfeng mkhudyakov karthikkosigi mrinalsharma legendartur wf141732 devcarneiro ia3andy weikio h3nrique huuhoait kumarinstor divyansh1908 dbrugger946 ashishkrishna1 shahid-roofi-khan dmvolod nf3lix qpc-github venkatesh82 vandanasinha zetfactor aspirina765 codersatheesh mcarlett booper-sinara ammachado lukaslonnroth durgapmenon fluctuationqt shashwath-sk geoffallendev abdulhakimzatar noir-madlax leena8686 apersonintech javedfaruquee1 f-ambroz ibidarmajaya thomas-gantenbein-tga hurzelpurzel risecai stefanhuber amir-zarchini victorchapman dskyrim925 dev-ds22 brunomendola talismancloud sekikn gdraganic mvolf bryanchance polaristech-io dirigiblelabs dewarthim vijaybharwani yuhucheng

camel-karavan's Issues

[VS Code]Unreadable hover with light theme in drop down of properties

First click on -/+ of spinner is clearing the field on creation

Workaround, add a value back and then the spinner is working

Implement doTry/doCatch

Missing versions of Native

The last version delivered as native is more than 2 months old in the docker repository under entropy1

Karavan cloud mode: Add Consumer options when create new flow.

Karavan cloud mode only shows a "from" option when create a new flow.

Property/parameter with empty value should not be in YAML

Unsupported field: when on org.apache.camel.model.WhenDefinition

Integration yaml

apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  name: hello-world
spec:
  flows:
    - from:
        uri: 'kamelet:timer-source'
        parameters:
          period: 3000
          message: Hello World
        steps:
          - choice:
              when:
                - when:
                    steps:
                      - to:
                          uri: 'kamelet:log-sink'
                          parameters:
                            showStreams: true
                    expression:
                      csimple: '${body} == "Hello World"'
              otherwise:
                steps:
                  - log:
                      logName: demo
                      loggingLevel: INFO
                      message: '${body}'

Exception:

java.lang.IllegalArgumentException: Unsupported field: when on org.apache.camel.model.WhenDefinition
	at org.apache.camel.dsl.yaml.common.YamlDeserializerBase.handleUnknownProperty(YamlDeserializerBase.java:110)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:104)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
	at org.apache.camel.dsl.yaml.common.YamlDeserializationContext$1.construct(YamlDeserializationContext.java:179)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asType(YamlDeserializerSupport.java:339)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asCollection(YamlDeserializerSupport.java:317)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatCollection(YamlDeserializerSupport.java:298)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatList(YamlDeserializerSupport.java:272)
	at org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ChoiceDefinitionDeserializer.setProperty(ModelDeserializers.java:1534)
	at org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$ChoiceDefinitionDeserializer.setProperty(ModelDeserializers.java:1498)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:103)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
	at org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:221)
	at org.apache.camel.dsl.yaml.deserializers.ProcessorDefinitionDeserializer.construct(ProcessorDefinitionDeserializer.java:36)
	at org.apache.camel.dsl.yaml.common.YamlDeserializationContext$1.construct(YamlDeserializationContext.java:179)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asType(YamlDeserializerSupport.java:339)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asCollection(YamlDeserializerSupport.java:317)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatCollection(YamlDeserializerSupport.java:298)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.asFlatList(YamlDeserializerSupport.java:272)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerSupport.setSteps(YamlDeserializerSupport.java:388)
	at org.apache.camel.dsl.yaml.deserializers.OutputAwareFromDefinitionDeserializer.setProperties(OutputAwareFromDefinitionDeserializer.java:71)
	at org.apache.camel.dsl.yaml.deserializers.OutputAwareFromDefinitionDeserializer.setProperties(OutputAwareFromDefinitionDeserializer.java:33)
	at org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:51)
	at org.apache.camel.dsl.yaml.common.YamlDeserializationContext$2.construct(YamlDeserializationContext.java:221)
	at org.apache.camel.dsl.yaml.YamlRoutesBuilderLoader$1.configure(YamlRoutesBuilderLoader.java:49)
	at org.apache.camel.builder.RouteBuilder.checkInitialized(RouteBuilder.java:541)
	at org.apache.camel.builder.RouteBuilder.configureRoutes(RouteBuilder.java:487)
	at org.apache.camel.builder.RouteBuilder.addRoutesToCamelContext(RouteBuilder.java:462)
	at org.apache.camel.impl.engine.AbstractCamelContext.addRoutes(AbstractCamelContext.java:1150)
	at org.apache.camel.main.RoutesConfigurer.configureRoutes(RoutesConfigurer.java:211)
	at org.apache.camel.quarkus.main.CamelMain.configureRoutes(CamelMain.java:70)
	at org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:555)
	at org.apache.camel.quarkus.main.CamelMain.initCamelContext(CamelMain.java:116)
	at org.apache.camel.quarkus.main.CamelMain.doInit(CamelMain.java:86)
	at org.apache.camel.support.service.BaseService.init(BaseService.java:83)
	at org.apache.camel.quarkus.main.CamelMain.startEngine(CamelMain.java:137)
	at org.apache.camel.quarkus.main.CamelMainRuntime.start(CamelMainRuntime.java:49)
	at org.apache.camel.quarkus.core.CamelBootstrapRecorder.start(CamelBootstrapRecorder.java:45)
	at io.quarkus.deployment.steps.CamelBootstrapProcessor$boot-173480958.deploy_0(CamelBootstrapProcessor$boot-173480958.zig:101)
	at io.quarkus.deployment.steps.CamelBootstrapProcessor$boot-173480958.deploy(CamelBootstrapProcessor$boot-173480958.zig:40)
	at io.quarkus.runner.ApplicationImpl.doStart(ApplicationImpl.zig:581)
	at io.quarkus.runtime.Application.start(Application.java:101)
	at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:101)
	at io.quarkus.runtime.Quarkus.run(Quarkus.java:66)
	at io.quarkus.runtime.Quarkus.run(Quarkus.java:42)
	at io.quarkus.runtime.Quarkus.run(Quarkus.java:119)
	at io.quarkus.runner.GeneratedMain.main(GeneratedMain.zig:29)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at io.quarkus.bootstrap.runner.QuarkusEntryPoint.doRun(QuarkusEntryPoint.java:48)
	at io.quarkus.bootstrap.runner.QuarkusEntryPoint.main(QuarkusEntryPoint.java:25)

Choice always contains Otherwise option

User should be able to add/remove Otherwise for Choice

CamelJBang improvements

Configure --max-messages
Configure --debug-level
One terminal per integration

Select step tab not readable

When following Development Karavan app the Select step modal is

DSL elements in YAML should be Kebab Case

Karavan read/write DSL elements in Camel Case but Camel YAML DSL supports Kebab Case only

Add trait support for CRD

https://camel.apache.org/camel-k/1.8.x/traits/traits.html

Select step - Sort A..Z case insensitive

I noticed that gRPC is listed last because it starts with lower case.

YAML REST DSL support

Beans support

Make a script to change version in all modules

Show default values in the option editor

The default value for the period in the chuck norris kamelet is 10000
https://github.com/apache/camel-kamelets/blob/main/chuck-norris-source.kamelet.yaml#L24

It would be nice to see this value somewhere in the options editor (maybe in description, tooltip, or as a text below the input field.)

[VS Code] Show the filename in the window title of Karavan UI editor

In vs code it would be nice to show the file name of what you edit, as that can be a bit harder to know.

Maybe show Karavan - hello.yaml where the red circle is

User should be able to add new step between existing steps

URI creation/extraction does not work for components with syntax that contains special symbols

Ex. netty-http

Deleting an element should clear the properties panel too

currently, it keep the property panel with elements corresponding to the deleted node

Error during Generate Camel Models ad API for Typescript

I got this error during

mvn clean compile exec:java -Dexec.mainClass="org.apache.camel.karavan.generator.KaravanGenerator" -f karavan-generator

seems like it is related to https://github.com/apache/camel-karavan/blob/main/karavan-generator/src/main/java/org/apache/camel/karavan/generator/CamelModelGenerator.java#L133, "CamelApi.camelize.tx" should be "CamelAPI.camelize.tx"

Apache License headers

The source code should have ASF license headers

pom.xml
java source
type script source

And potentially others, such as Dockerfile.

Creating a new flow - CRD what does it mean

When creating a new flow, there is a [x] for CRD.

I think end users will not understand what it means. We should have a description what it means to turn this on or off.

[VS Code]Unreadable Producer and consumer with light theme

after clicked on "add flow"

No advanced options

When there are no advanced options, then maybe we should remove that blue "Advanced parameter

s"

Icon on right marking producers are overlapping when using a choice

Implement search for Kamelets and Components selector

Standalone does not support direct uri edition

When creating a new route using the standalone app there is no way to edit the from: URI.

Could not read yaml with kebab-case EIP

User should be able to reorder steps

Standalone - You loose the current integration if you click away

I was editing a new integration and then clicked "Kamelets" and then I lost my current integration.

Durations doesn't support notation with letters

For instance for period of timer, we cannot write 1d

Move Add Flow button to top menu bar

I think its a little bit confusing that "Add flow" button is soo prominent on the screen that you think you need to click this button to add a new step. Instead you need to however the mouse at the EIP and then the + sign appears.

Should we move "Add flow" to the top right where the other buttons are "Copy" and "Save".

And it can be named "Add new flow" then you better understands its a new flow (route) and not a ste

p

Standalone mode - 0.0.6 in web ui and 0.0.7 in quarkus

Running the latest standalone mode in JVM via docker and noticed the version number difference.

JBang live reload

We have support for live reload in Camel 3.14.0
https://issues.apache.org/jira/browse/CAMEL-17206

So you can run

jbang -Dcamel.jbang.version=3.14.0-SNAPSHOT CamelJBang@apache/camel run my-route.yaml --reload

VS Code: Create a karavan integration through new file

In VS Code a new Karavan integration is created with right-click on a folder in the explorer.

As an alternative this could be by creating a new file.

For example:

A) Create new file

Ctrl+N
File --> New File

B) A new file opens and user have the possibility to 'select a language'

C) YAML (Karavan integration) (note: similar to create for example Docker (dockerfile))

Standalone loads all YAML file from directory

When using the Standalone application in LOCAL mode, it reads all the YAML files in the integrations folder as Integrations even if those files represent something else.

Maybe we need a validation that the Kind: is correct, or parse a schema perhaps?

Could not read yaml with Implicit Expression field

User should be able to use custom Kamelets

[VS Code] Message "File is not Camel-K Integration!" can be erroenous

in case of minimal Camel K files, the message is displayed. the message shoudl be more precise and mention that it is not a (?) Kubernetes Camel K file?

fo risntance with file https://github.com/apache/camel-k/blob/main/examples/languages/routes.yaml :

- from:
    uri: "timer:tick"
    parameters:
      period: "5000"
    steps:
      - set-body:
          constant: "Hello Yaml !!!"
      - transform:
          simple: "${body.toUpperCase()}"
      - to: "log:info"

Right-click and click "Karavan: Open in Designer"

JBang run mode

We should get this working. After installing jbang (such as via sdk) then we should make jbang run via its alias

Today it runs as

~/workspace/camel-k/examples/languages main ❯ CamelJBang run routes.yaml --max-messages=10 --debug-level=info
zsh: command not found: CamelJBang

But that does not work. You have then to copy the CamelJBang.java source file to same dir, rename to not have .java and make it executable. And fix the RELEASE to say 3.13.0.

But if we run via the alias then it should run with the latest release

jbang CamelJBang@apache/camel run routes.yaml --max-messages=10 --debug-level=info

Add the option to save/export only the routes and not the integration for standalone

Add an option to export the yaml flow without the surrounding metadata related to the integration.

Instead of

apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  name: integration1
spec:
  flows:
    - from:
        parameters:
          period: 3000
        steps:
          - log:
              logName: result
              loggingLevel: INFO
              message: '${body}'
        uri: 'kamelet:chuck-norris-source'

just this:

# camel-k: language=yaml

- from:
    uri: 'kamelet:chuck-norris-source'
    parameters:
      period: 3000
    steps:
      - to: "log:info"```

Dragged element disappears when dropped into its child

Upgrade to camel-kamelets 0.5.0

no such file or directory

After creating of a karavan yaml file in VSCode I get the following message:

Error: ENOENT: no such file or directory, open 'C:\c:\Users\me\Documents\workspace\test\test.yaml'

The file is editable, but doesn't seem to save (because of the double drive letter). After restart the yaml is gone.

OS: Windows 10 (Windows_NT x64 10.0.19043)
Version: 1.61.2 (user setup)
Commit: 6cba118ac49a1b88332f312a8f67186f7f3c1643
Date: 2021-10-19T14:57:20.575Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0

Implicit to EIP DSL

Karavan should support implicit to EIP DSL, like:

- to: "log:info"

kamel init foo.yaml

And want to turn off show-body-type and show-exchange-pattern on the log endpoint, then you have to

turn it on
turn it off

The issues is that they are on by default, but the UI do not represent this, as the UI shows it as off.