[
https://issues.apache.org/jira/browse/CAMEL-22616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18094020#comment-18094020
]
Claus Ibsen commented on CAMEL-22616:
-------------------------------------
*TODO: Metadata / Tooling gap*
The camel.cluster.<type>.* options metadata (JSON) cannot be computed inside
camel-main because the options are defined on cluster service classes in
external component JARs (camel-file, camel-kubernetes, etc.). The bean JSON
metadata already exists per-component (e.g., FileLockClusterService.json with
all options, types, defaults, descriptions), but there is no bridge connecting
the camel.cluster.file.* prefix to FileLockClusterService properties in the
camel-main-configuration-metadata.json that tooling consumes. This needs
catalog/tooling enhancement to discover cluster types via @JdkService
annotations and map their bean metadata to the camel.cluster.<type>.* property
namespace.
> camel-jbang - Add support for camel.cluster.xxx configurations
> --------------------------------------------------------------
>
> Key: CAMEL-22616
> URL: https://issues.apache.org/jira/browse/CAMEL-22616
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.22.0
>
>
> We have support for this in CSB
> [https://camel.apache.org/manual/clustering.html]
> Where there are auto configuration of camel.cluster.file / camel.cluster.xxx
> and so on. We should look at adding this to camel-main / camel-jbang so we
> can do this as well there, and then when exporting to CSB/CEQ then it works
> there too.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
