jamesnetherton opened a new issue, #6339: URL: https://github.com/apache/camel-quarkus/issues/6339
### Bug description If you do: ``` export CAMEL_QUARKUS_START_MOCK_BACKEND=false ``` Then run any native tests (E.g `azure-storage-blob` & `google-storage`) where `MockBackendUtils.startMockBackend` is used at runtime (I.e. in non-test code), you'll find the results aren't as you expect. It's because the result of `startMockBackend` returns `true`, regardless of what is set in the environment. IIRC, a recent(ish) change in Quarkus meant that build time environment variables would not propagate into the native image (since it's a potential security risk). We should probably avoid [this](https://github.com/apache/camel-quarkus/blob/main/integration-tests-support/mock-backend/src/main/java/org/apache/camel/quarkus/test/mock/backend/MockBackendUtils.java#L24-L25) static lookup and just get the config value on each request. The overhead it trivial. -- 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: commits-unsubscr...@camel.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
