Ricardo M.

Ok, if I'm understanding correctly, in this case, the `dataSource` field should allow to create or select existing beans but without having a `#` prefix.

yup, I saw that part as well. Judging by the list of custom features this field might require, I think it would be better to provide something custom for this...

For this, let's start by listing the differences between both forms. (Metadata editor vs Kamalet configuration editor)

Closing this PR for now, pending updating it with the latest `main` and picking the colors.

Here's my proposal on how to move forward with this: 1. Add a container for individual routes only 2. Add the underlying element to be configured in the Canvas Form...

An example:  Example route ```yaml - route: id: customer-post-route from: id: from-1165 uri: rest parameters: bindingMode: off consumes: application/json inType: "" method: post path: /customer uriTemplate: /{customerId} steps: -...

It's possible this needs to be addressed in the Camel YAML DSL schema directly

Please @igarashitm, when you have time, could you take a quick look?

The available routes list should be: - Available direct endpoints - Rest OpenAPI operation IDs (in case using OpenAPI)

Needs to be checked how to reproduce