Revisiting catalogs & schema

[igarashitm]

Recently we integrated the properties schema generated from the main schema camelYamlDsl.json into catalogs. Now we have proiertiesSchema property on the catalogs of components, dataformats, languages and patterns, as well as kamelets (kamelets-aggregate.json). In this way, while we can preserve additional data that is defined in the catalog and deliver to the UI, we also provide the properties JSON schema that is consumable for Ajv and uniforms.

Going forward along this way, we might no longer need the original schema files itself for ui. Maybe keep the original schema file camelYamlDsl.json only for source code editor?, but remove the sub-schemas for each element.

One thing that has to be done before that is to integrate schema for non-visual configurations, such as beans. Couple of things to handle

1. The catalog for beans top element has been removed. However there is a new catalog models-app/bean.json which describes a single entry of beans. we can leverage this for Camel Route beans editor.
2. Other configurations like routeConfiguration, errorHandler, onException stays in models
3. It might be better to have a separate catalog for Camel-K CR. For example, Kamelet uses RouteTemplateBeanDefinition which is different schema from Camel Route beans. An option is to create a camel-catalog-aggregate-kamelet.json and put that into it. And camel-catalog-aggregate-pipe.json would have our Pipe ErrorHandler entry
   1. Where do we want k8s metadata? in common file or in each catalog file of CRs? We might want it in each catalog file of CRs, and the metadata schema might need to be customized. For example kamelet metadata schema might define kamelet specific annotations in the schema or catalog

Let's use here to make our needs clearer and identify the action items. Any feedback is more than welcome!

[igarashitm]

• Support routeConfiguration #492
  I plan to introduce an artificial catalog category, entity, to put all @YamlIn properties catalog together - the top level properties in Camel YAML DSL, including route, from, beans, routeConfiguration, rest and etc. - as well as combining the schema extracted from camelYamlDsl.json as propertiesSchema onto the catalog.
  • We might also want to put rest sub steps like get, post etc. into this category