davsclaus commented on issue #3117: URL: https://github.com/apache/camel-kamelets/issues/3117#issuecomment-6974377053
Status on 2026-11-18. The catalog has 234 Kamelets after the removals in #3165, #3166 and #3167: | Type | Kamelets | With `types` | Only `headers` | No `dataTypes` | |---|---|---|---|---| | source | 82 | 16 | 58 | 8 | | sink | 94 | 3 | 61 | 30 | | action | 58 | 0 | 25 | 33 | The documentation PRs (#3141 to #3155) added only `headers` blocks, which list the headers a Kamelet reads or sets. `types` are still declared only on the same 19 Kamelets. **A `default` data type is not only metadata.** This changes the plan above. `KameletRoutesBuilderLoader` makes the `default` the route's `inputType` or `outputType`, so Camel runs its transformer on every message. I tested it with `camel run`: `log-sink` with `in.default: application-octet-stream` turned a String body into a `byte[]` and set `Content-Type`. So adding a `default` changes how the Kamelet behaves. Each Kamelet then needs a test and an upgrade note. A `types` entry without a `default` is not run. `camel_catalog_kamelet_doc` of the Camel MCP server shows it, but the YAML validator follows only the `default`. To decide: - **`types` without a `default`:** no change at runtime, but the validator learns nothing. - **A `default`, added Kamelet by Kamelet with tests:** the validator learns the body, but each one changes behaviour. _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]
