Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
4.5.0
-
None
-
Jbang version : 0.115.0
Camel version: 4.5.0
Camel k: 2.3.0-SNAPSHOT
-
Unknown
Description
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:
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
will result in the following integration CRD configuration:
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
In comparaison the kamel command:
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
will result in the following integration CRD configuration:
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
Note: I did not test it but I suspect 4.4.x might be affected as well.