[
https://issues.apache.org/jira/browse/CAMEL-20645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855828#comment-17855828
]
Gaëlle Fournier edited comment on CAMEL-20645 at 6/18/24 8:05 AM:
------------------------------------------------------------------
I think, after more testing, that we need something more than what is described
in the bug. What we need is to be able to configure "Camel-k" version like what
can be done in .camel-jbang-user.properties, with a command like
{code:java}
camel k set camel-k-version xxx{code}
. The best place to store it, from what I can see, would be the
.camel-jbang-plugins.json file.
[~christophd] [~claudio4j]
was (Author: JIRAUSER299686):
I think, after more testing, that we need something more than what is described
in the bug. What we need is to be able to configure "Camel-k" version like what
can be done in .camel-jbang-user.properties, with a
{code:java}
camel k set camel-k-version xxx{code}
. The best place to store it, from what I can see, would be the
.camel-jbang-plugins.json file.
[~christophd] [~claudio4j]
> camel-jbang-plugin-k run command telemetry trait parameters ignored
> -------------------------------------------------------------------
>
> Key: CAMEL-20645
> URL: https://issues.apache.org/jira/browse/CAMEL-20645
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Affects Versions: 4.5.0
> Environment: Jbang version : 0.115.0
> Camel version: 4.5.0
> Camel k: 2.3.0-SNAPSHOT
> Reporter: Gaëlle Fournier
> Priority: Minor
> Fix For: 4.x
>
>
> When running the telemetry test from Camel K with jbang camel k plugin, the
> telemetry trait parameters are ignored in the generated Integration CRD.
> The jbang camel k command:
> {code}
> jbang run --deps=org.apache.camel:camel-jbang-plugin-k:4.5.0
> --deps=org.apache.camel.k:camel-k-crds:2.3.0-SNAPSHOT camel@apache/camel k
> run e2e/telemetry/files/rest-consumer.yaml --name rest-consumer -t
> telemetry.enabled=true -t
> telemetry.endpoint=http://opentelemetrycollector.otlp.svc.cluster.local:4317{code}
> will result in the following integration CRD configuration:
> {code:java}
> spec:
> flows:
> - rest:
> get:
> - path: /customers/{name}
> to: direct:start
> - from:
> steps:
> - log:
> message: get ${header.name}
> - setBody:
> simple: ${header.name} Doe
> uri: direct:start
> traits: {}
> status:
> dependencies:
> - camel:core
> - camel:direct
> - mvn:org.apache.camel.k:camel-k-runtime
> - mvn:org.apache.camel.quarkus:camel-quarkus-platform-http
> - mvn:org.apache.camel.quarkus:camel-quarkus-rest
> - mvn:org.apache.camel.quarkus:camel-quarkus-yaml-dsl{code}
>
> In comparaison the kamel command:
> {code:java}
> kamel run e2e/telemetry/files/rest-consumer.yaml --name rest-consumer -t
> telemetry.enabled=true -t
> telemetry.endpoint=http://opentelemetrycollector.otlp.svc.cluster.local:4317{code}
> will result in the following integration CRD configuration:
> {code:java}
> spec:
> flows:
> - rest:
> get:
> - path: /customers/{name}
> to: direct:start
> - from:
> steps:
> - log:
> message: get ${header.name}
> - setBody:
> simple: ${header.name} Doe
> uri: direct:start
> traits:
> addons:
> telemetry:
> enabled: true
> endpoint: http://opentelemetrycollector.otlp.svc.cluster.local:4317
> status:
> dependencies:
> - camel:core
> - camel:direct
> - mvn:org.apache.camel.k:camel-k-runtime
> - mvn:org.apache.camel.quarkus:camel-quarkus-opentelemetry
> - mvn:org.apache.camel.quarkus:camel-quarkus-platform-http
> - mvn:org.apache.camel.quarkus:camel-quarkus-rest
> - mvn:org.apache.camel.quarkus:camel-quarkus-yaml-dsl{code}
>
> Note: I did not test it but I suspect 4.4.x might be affected as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
