[camel-karavan] branch main updated: Roadmap

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

marat pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-karavan.git


The following commit(s) were added to refs/heads/main by this push:
     new 1e0470f  Roadmap
1e0470f is described below

commit 1e0470f6f92197be31b9779b75b1dbc37f8e3b5f
Author: Marat Gubaidullin <ma...@gmail.com>
AuthorDate: Thu Oct 6 17:47:42 2022 -0400

    Roadmap
---
 ROADMAP.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 48 insertions(+)

diff --git a/ROADMAP.md b/ROADMAP.md
new file mode 100644
index 0000000..76c8dfd
--- /dev/null
+++ b/ROADMAP.md
@@ -0,0 +1,48 @@
+# Roadmap
+
+## Visual debugging and tracing
+Karavan users can already  package, build and deploy integrations in one click.
+However a real integration development process is iterative and requires debugging.
+
+Visual debugging process will be implemented, so users will be able stopping/stepping running routes and have access to exchange data (body, headers, properties)  
+
+## Monitoring and dashboards
+We are planning to create a Dashboard page in the Karavan cloud application.
+
+Dashboard should show all Deployments, Pods, Pipelines and camel-context health-check information associated with Camel projects. 
+Camel projects are projects labeled with `app.openshift.io/runtime=camel` or `app.openshift.io/runtime=camel` and not limited to Karavan-created projects.
+
+## Camel Error Handler
+ErrorHandler YAML DSL is different from canonical Java/XML DSL.
+We need first to synchronize DSLs and then generate visual elements for error handling.
+
+## Propagation between environments
+Current version of Karavan deploys integration images (using Tekton pipeline) in the dev environment (same namespace where karavan application deployed).
+
+We are considering implementing integration propagation between dev and test/prod environment as an immutable image that is already in the image repository. Users should be able to select imageId to be propagated. 
+
+## Kubernetes Operator
+To simplify Karavan installation in Kubernetes/Openshift we have been working on Karavan Operator.
+
+## Access Control
+The following access control are planning to be implemented:
+
+1. Role-Based Access Control (RBAC)
+    * Developer creates project, routes, rest api, build and deploy
+    * Viewer has view-only access
+    * Administrator could change projects templates and default values
+2. Group-Based Access Control
+    * Each project has a group in Keycloak (with the same name)
+    * Only group member could have access to the project
+
+## Web-based IDE 
+To support web-based IDEs like Gitpod, DevSpaces, GitHub Codespaces, etc, web-extension specific configuration will be added to Karavan VS Code extension.
+
+Karavan will also be published in the Open VSX marketplace.
+
+## Data mapping
+The most requested feature for Karavan is Data Mapping.
+
+We are analyzing existing open-source data mapping solutions like AtlasMap that might be embedded into Karavan Designer. 
+
+Another option is to implement dedicated Camel-specific data mapping functionality that take into consideration Camel Exchange structure and can leverage Camel data transformation functionality and built-in Expression languages.