davsclaus opened a new issue, #2869:
URL: https://github.com/apache/camel-kamelets/issues/2869
## Summary
The four Jira sink kamelets (`jira-add-comment-sink`, `jira-add-issue-sink`,
`jira-transition-issue-sink`, `jira-update-issue-sink`) all included
`accessToken: "{{?personal-token}}"` as an optional endpoint parameter. When
the `personal-token` property is not provided by the user, the
`{{?personal-token}}` placeholder remains unresolved inside a `RAW()` wrapper,
which causes the Jira endpoint to silently fail to be created.
The route ends up as `Route[kamelet://source -> null]` — messages flow
through the kamelet but never reach the Jira endpoint. Exchanges complete
"successfully" (0 failures) because the Jira endpoint is simply never invoked.
## Root Cause
When the Camel endpoint URI factory constructs the endpoint URI, optional
`{{?...}}` placeholders that are not resolved get wrapped in `RAW()`. The
resulting URI contains `accessToken=RAW({{?personal-token}})` which is not a
valid value, causing the endpoint creation to fail silently. The `to` step in
the route template is effectively dropped.
This only affects `to` (producer) endpoints in sink kamelets. The same
pattern in `from` (consumer) endpoints (e.g., `jira-source`) works correctly.
## Affected Kamelets
- `jira-add-comment-sink.kamelet.yaml`
- `jira-add-issue-sink.kamelet.yaml`
- `jira-transition-issue-sink.kamelet.yaml`
- `jira-update-issue-sink.kamelet.yaml`
## Fix
Remove `accessToken: "{{?personal-token}}"` from the endpoint parameters in
all four sink kamelets. The `personal-token` property definition remains in the
spec for users who want to provide it, but it should not be auto-mapped into
the endpoint URI as an optional parameter.
## Note
This may also be a Camel core issue — optional parameters that remain
unresolved should probably not cause silent endpoint creation failure. Consider
filing a follow-up in `apache/camel` if the runtime should handle this more
gracefully (e.g., strip unresolved optional params before endpoint creation, or
log a warning).
--
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]
