Claus Ibsen created CAMEL-26294:
-----------------------------------
Summary: camel-yaml-dsl-validator - camel validate reports Kamelet
and language options that work at runtime
Key: CAMEL-26294
URL: https://issues.apache.org/jira/browse/CAMEL-26294
Project: Camel
Issue Type: Bug
Reporter: Claus Ibsen
Fix For: 4.24.0
A sweep of the code blocks of the documentation through the checks of camel
validate source (see CAMEL-26293) found three kinds of options the validator
reports as wrong, although Camel takes them when the route runs:
* *Options a Kamelet forwards with advancedOptions.* With advancedOptions:
true, the extra options of a Kamelet endpoint go to the endpoint the Kamelet
wraps, but the validator reports them as unknown properties of the Kamelet:
kamelet-component.adoc, kamelet:aws-s3-source with maxConnections: 100
("unknown property 'maxConnections'").
* *Kamelet properties in application.properties.*
camel.component.kamelet.<kamelet>.<property> keys are reported as unknown
options (kubernetes-secrets-component.adoc,
property-placeholder-functions.adoc:
camel.component.kamelet.postgresql-sink.databaseName ...). And a route whose
required Kamelet properties come from these keys is reported for the missing
properties (kubernetes-secrets-component.adoc: kamelet:postgresql-sink, "the
required properties password, serverName, username are missing").
* *Language options that are not in the catalog.*
camel.language.<name>.<property> is bound to the setters of the language, but
the validator only knows the options of the catalog:
camel.language.typesafe-ai.endpoint, threshold and state
(typesafe-ai-language.adoc), and camel.language.quickjs.engineMaxMemory and
engineMaxEvaluations (quickjs-language.adoc). The fix may be in the catalog
(declare these options of the language) rather than in the validator.
All three make camel validate, the MCP camel_validate_source tool and the
editor of the Camel CLI reject a working configuration, which an AI assistant
then tries to fix.
_Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
