Lukas Lowinger

@zhfeng I don't have any info about existing elasticsearch tests with SSL, so from my POV no.

I can confirm it - i was trying it today and hit the same issue. Also i had to set Callback URL to `https://127.0.0.1/` in Postman.

Just adding note about https://github.com/apache/camel-quarkus/blob/3.25.0/integration-test-groups/foundation/core/src/test/java/org/apache/camel/quarkus/core/CoreTest.java#L171 from @jamesnetherton : ``` There is some weirdness in Camel with classpath resource scanning depending on how apps are packaged / run. So TODO was...

@kaushal540 In which version of localstack i can verify it ?

Another failure spotted by @jamesnetherton in https://github.com/apache/camel-quarkus/actions/runs/17756464238/job/50461538810?pr=7743

@squakez There is regression from camel-quarkus-opentelemetry. 3.20 (6 traces, all with camel metadata): 3.26 (8 traces, including 2 from quarkus vert.x without camel metadata):

I'm talking about regression in the camel-quarkus-observability-example. Where with 3.20 it was returning different number of spans than it returns with 3.26. And it is because 3.26 is missing similar...

Ie. when i deleted content of https://github.com/apache/camel-quarkus/blob/main/extensions/opentelemetry/runtime/src/main/java/org/apache/camel/opentelemetry/CamelQuarkusOpenTelemetryTracer.java locally, i can see 8 spans (the same as in 3.26). So even camel-quarkus-opentelemetry was able to consume 3rd party library (quarkus vertx).

@squakez Thanks for the input. Ad `I am not sure what was the rationale to remove the Vertx spans, but, as a user, I'd be more keen to keep them...

@squakez Yes, they are not identical, but from Camel point of view, they should be. I use camel component (with quarkus runtime), so i want to see just camel spans...