Closed zhfeng closed 2 years ago
The DevServicesConfigBuildItem
property looks like be merged from the previous runs, refer to
https://github.com/quarkusio/quarkus/blob/main/core/deployment/src/main/java/io/quarkus/deployment/steps/DevServicesConfigBuildStep.java#L34-L48
So it should to produce RunTimeConfigurationDefaultBuildItem
instead of DevServicesConfigBuildItem
for camel.component.kafka.brokres
So, we are in the case where dev services were enabled (default value) and then explicitly disabled. But then Quarkus passes /merges the previous broker url from old generation to the new one. Is my understanding correct at this stage ?
If yes, then isn't it a Quarkus bug ?
@aldettinger yeah, you're correct. I'm not sure this is a bug or a design feature. It could be worth to open a Quarkus issue to get some explains.
@zhfeng From quarkus-dev discussion, it looks there are more investigation. Should we re-open this ticket then ? Or maybe have a follow up issue ?
@aldettinger yeah, I'm testing with Stuart's fix. And creat a follow up issue if the fix works.
The upstream Quarkus https://github.com/quarkusio/quarkus/pull/20964 can fix the failure tests. The following https://github.com/apache/camel-quarkus/issues/3227 will be fixed in quarkus-main.
Currently if
KafkaDevServicesDisabledTest
is running afterKafkaDevServicesEabledTest
, it is failing withIt looks like the kafka dev service is avaible during all the test phase regardless of the test is restarted even if
quarkus.kafka.devservices.enabled=false
is configed.It might be a bug somewhere in Quarkus DevService.