Description
We have more and more properties that can be set via camel-main.
We can look at when using @Configurer to generate type-safe and reflection free configuration then we can also generate tooling metadata (json files) that we can use for the website and tooling.
Today we generate a single camel-main json file that has all of them. But it may be worth to be able to externalize these into individual files, so we can have them seperated.
For example dev consoles can likely be custom per component so they will not be in core, but in the component. And so it would be worth to have a way of generate tooling medata for them also.
We can either consider a json file that is specific for a dev-console or something generic with configurer.
Then we can see also if we can use this for dev consoles that can be made work in both jbang, main, quarkus and spring boot.
Attachments
Issue Links
- relates to
-
CAMEL-16234 camel-main - Allow 3rd party components to offer configuration options
-
- Open
-