Claus Ibsen created CAMEL-24744:
-----------------------------------

             Summary: camel-jbang - the YAML the MCP scaffold tools, the camel 
init templates and the bundled examples generate is in the deprecated compact 
notation; write it in the canonical format
                 Key: CAMEL-24744
                 URL: https://issues.apache.org/jira/browse/CAMEL-24744
             Project: Camel
          Issue Type: Improvement
          Components: camel-jbang
            Reporter: Claus Ibsen


The compact notation is deprecated (CAMEL-24722 rewrote the hints, CAMEL-24723 
reports it in {{camel validate yaml --canonical}} and warns at runtime), but 
what camel-jbang itself generates is still written in it, so a user or an AI 
agent starting from a Camel-generated file starts from the deprecated form and 
{{camel run}} warns on the first run:

* the MCP scaffold tools: {{AiPipelineScaffoldTools}} ({{- simple: "${body} 
contains 'invoice'"}} in a when) and {{OpenApiTools}} ({{constant: "TODO: 
implement ..."}})
* the {{camel init}} templates {{integration.yaml.ftl}}, 
{{kamelet-source.yaml.ftl}}, {{kamelet-action.yaml.ftl}} ({{setBody: {simple: 
...}}}, {{- log: "..."}})
* the bundled examples under {{camel-jbang-core/src/main/resources/examples}} 
(tui-hello-world, message-size, orders)

Write them in the canonical format ({{expression: {simple: {expression: 
"..."}}}}, {{log: {message: "..."}}}) and guard them: the templates and 
examples through {{camel validate yaml --canonical}} in a test, the scaffold 
tools through their existing tests asserting the canonical form.

Noted on CAMEL-24722.



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

Reply via email to