[camel-karavan] branch main updated: Update ROADMAP.md

[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 502434d6 Update ROADMAP.md
502434d6 is described below

commit 502434d63cf2e220e84f820314903bb53df93db0
Author: Marat Gubaidullin <ma...@gmail.com>
AuthorDate: Mon Apr 3 11:44:39 2023 -0400

    Update ROADMAP.md
---
 ROADMAP.md | 37 +++++++++++++++++++------------------
 1 file changed, 19 insertions(+), 18 deletions(-)

diff --git a/ROADMAP.md b/ROADMAP.md
index 8fb5ebc3..33de1765 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -1,29 +1,35 @@
-# Roadmap
+# Roadmap 2023
 
-## Visual debugging and tracing
+## Done:
+### 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.
+
+### 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.
+
+### Kubernetes Operator
+To simplify Karavan installation in Kubernetes/Openshift we have been working on Karavan Operator.
+
+## TODO:
+### 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
+### 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. Projects should not be 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
+### 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
+### Access Control
 The following access control are planning to be implemented:
 
 1. Role-Based Access Control (RBAC)
@@ -34,12 +40,7 @@ The following access control are planning to be implemented:
     * 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
+### 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.