davsclaus opened a new pull request, #3079:
URL: https://github.com/apache/camel-kamelets/pull/3079
`earthquake-source` writes `setBody: {exchange-property: lastUpdate}` and
`azure-storage-blob-changefeed-source` writes `marshal: {json:
{module-class-names: ...}}`.
**Nothing is broken** — the runtime accepts both spellings; I ran a route
with `setBody: {exchange-property: ...}` and it resolved the property
correctly. But these are the only two of the 250 kamelets written that way, the
Camel YAML DSL schema lists only `exchangeProperty` and `moduleClassNames`, and
so any tooling that validates against the schema reports them.
`earthquake-source` already writes `exchangeProperty` in a Simple expression a
few lines above the kebab-case one.
```diff
- exchange-property: lastUpdate
+ exchangeProperty: lastUpdate
- module-class-names:
com.fasterxml.jackson.datatype.jsr310.JavaTimeModule
+ moduleClassNames:
com.fasterxml.jackson.datatype.jsr310.JavaTimeModule
```
Both copies are updated: `kamelets/` and the copy under
`library/camel-kamelets/src/main/resources/kamelets` that the build keeps
beside it.
**How these were found, and what else the sweep showed.** I validated all
250 kamelets against the Camel YAML DSL schema while fixing CAMEL-25194 (the
validator was treating a `.kamelet.yaml` as a route file and rejecting every
one of them). After that fix, 250 kamelets produced 3 reports: these two, and
`fhir-sink`, which hits a schema bug unrelated to kamelets — it reproduces in a
plain route file with two `when` branches unmarshalling with different FHIR
data formats, and is being handled separately. With this change, 249 of 250
validate clean.
Verified afterwards: the camelCase form runs (`body is 2026-01-01` from the
same route), and both files validate clean.
_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]
