[jira] [Assigned] (CAMEL-24260) camel-spring-boot - Dev console to expose Spring Boot configuration metadata for TUI quick docs

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-24260:
-----------------------------------

    Assignee: Claus Ibsen

> camel-spring-boot - Dev console to expose Spring Boot configuration metadata for TUI quick docs
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-24260
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24260
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring-boot
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>              Labels: tui
>
> The TUI Source tab now supports inline quick docs (i key) for application.properties, showing catalog descriptions for camel.* properties. However, Spring Boot applications also use properties like management.endpoint.health.access, server.port, spring.datasource.url etc. that are not covered.
> Spring Boot bundles META-INF/spring-configuration-metadata.json in each starter JAR with property metadata (name, type, description, defaultValue). These JARs are on the running app's classpath but not the TUI's.
> Proposal: add a dev-console in camel-spring-boot that scans all spring-configuration-metadata.json resources on the classpath (via ClassLoader.getResources()), merges them, and exposes the combined metadata as a JSON endpoint. The TUI can then fetch this metadata alongside the existing camel-main catalog to provide quick docs for Spring Boot properties as well.
> This would involve:
> - New dev-console in camel-spring-boot module
> - StatusParser to parse the new metadata
> - SourceTab properties quick doc provider to use Spring Boot metadata as a fallback for non-camel.* properties



--
This message was sent by Atlassian Jira
(v8.20.10#820010)