davsclaus commented on PR #27447: URL: https://github.com/apache/camel/pull/27447#issuecomment-6021840184
More from the same side check, on a model writing its **own** Kamelet (a business building block), in f5fc8233f8ba. The step "write `tag-order-action`, then use it" passed 1 of 3 runs with tools. The traces showed mistakes the validator did not report: - `properties` and `required` directly under `spec`; - `required: true` on a property; - `do:` or `steps:` where `spec.template.from` goes; - a template starting `from: kamelet:tag-order-action/route`, so from itself, which recursed into a `StackOverflowError` at runtime; - `dependencies: [camel:simple]`, an artifact that does not exist, so a download failed on every reload. Changes: - `KameletChecks.validateKameletFile` checks the shape of a `.kamelet.yaml` file and its `camel:` dependencies. Run against the 262 Kamelets of camel-kamelets main, it flags only the 3 whose components Camel 4.23 removed (`splunk`, `json-patch`, see apache/camel-kamelets#3092). - `camel_catalog_sample name=kamelet` returned only routes that call a Kamelet, and was every model's first call. It now also returns the action Kamelet file from the guide. A name such as `kamelet-custom`, or `kind=kamelet`, gets the guide's Kamelet files. - `camel_catalog_doc` with `kind=kamelet` now reaches the guide (`docPage=custom`). That was a regression of this PR: a model asked 14 times. "Kamelet not found" and unknown names containing "kamelet" point to the guide, and the doc-pages hint names each page. - `kamelet-custom.adoc`: the samples are in canonical YAML DSL, the action sample comes first, and there is a short "Mistakes to avoid" section. Result: the custom Kamelet task passed **3 of 3** runs, both steps, with no errors, in 5 to 10 tool calls per step. camel-jbang-core passes 1562 of 1562. _Claude Code on behalf of Claus Ibsen_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
