[
https://issues.apache.org/jira/browse/CAMEL-26293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18131778#comment-18131778
]
Claus Ibsen commented on CAMEL-26293:
-------------------------------------
PR: https://github.com/apache/camel/pull/28438
_Claude Code on behalf of davsclaus_
> Docs - examples with options that do not exist or values Camel does not read
> ----------------------------------------------------------------------------
>
> Key: CAMEL-26293
> URL: https://issues.apache.org/jira/browse/CAMEL-26293
> Project: Camel
> Issue Type: Task
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> A sweep of the code blocks of every .adoc in the repository (YAML routes
> through the checks of camel validate source, JSON parsed, XML checked for
> well-formed, properties with camel.* keys validated) found five examples that
> are wrong:
> * route-configuration.adoc: the YAML route prints
> ${header.CamelTimerCounter}, but the timer sets CamelTimerCounter as an
> exchange property, and only with includeMetadata=true.
> * using-propertyplaceholder.adoc: elasticsearch:foo?query=... uses a query
> option that the elasticsearch component does not have (Java, XML and YAML).
> * aws-secrets-manager-component.adoc and security.adoc:
> camel.vault.aws.useDefaultCredentialProvider is
> camel.vault.aws.defaultCredentialsProvider, and
> CAMEL_VAULT_AWS_USE_DEFAULT_CREDENTIALS_PROVIDER=accessKey should be true.
> * security.adoc: the Google Secret Manager example sets
> camel.vault.aws.projectId instead of camel.vault.gcp.projectId.
> * opentelemetry2.adoc: camel.mdc.customHeaders is
> camel.mdc.customExchangeHeaders.
> The other findings are examples that are right where they are (fragments,
> Kamelets of the project, custom functions, a route that fails on purpose,
> Spring Boot properties).
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
