Kafka Streams Fails to create topology when topics-timeout is set to 0

[pcasaes]

Describe the bug

The docs state that when quarkus.kafka-streams.topics-timeout is set to 0 then topics checks is ignored.

https://quarkus.io/guides/all-config#quarkus-kafka-streams_quarkus-kafka-streams-topics-timeout

As of Quarkus 3.24.1 it fails to create the topology instead as it timeouts out when trying to check on the topics.

Expected behavior

Should ignore topics check and create the topology.

Actual behavior

2025-06-26 12:53:02,756 ERROR [io.quarkus.kafka.streams.runtime.KafkaStreamsTopologyManager] (executor-thread-1 - 50687)  - Failed to get topic names from broker: java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095)
	at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:173)
	at io.quarkus.kafka.streams.runtime.KafkaStreamsTopologyManager.waitForTopicsToBeCreated(KafkaStreamsTopologyManager.java:143)

How to Reproduce?

Create a topology with quarkus.kafka-streams.topics-timeout set to 0.

Output of uname -a or ver

HWCQFK90GX 24.3.0 Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:22 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6041 arm64

Output of java -version

openjdk version "21.0.6" 2025-01-21 LTS OpenJDK Runtime Environment Corretto-21.0.6.7.1 (build 21.0.6+7-LTS) OpenJDK 64-Bit Server VM Corretto-21.0.6.7.1 (build 21.0.6+7-LTS, mixed mode, sharing)

Quarkus version or git rev

3.24.1

Build tool (ie. output of mvnw --version or gradlew --version)

Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) Maven home: /Users/paulo.casaes/.sdkman/candidates/maven/3.9.9 Java version: 21.0.6, vendor: Amazon.com Inc., runtime: /Users/paulo.casaes/.sdkman/candidates/java/21.0.6-amzn Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "15.3.1", arch: "aarch64", family: "mac"

Additional information

I believe the issue was introduced by this PR #47863
@ozangunalp

The issue does not happen on 3.23.4

[quarkus-bot]

/cc @alesj (kafka,kafka-streams), @cescoffier (kafka), @gunnarmorling (kafka-streams), @ozangunalp (kafka,kafka-streams), @rquinio (kafka-streams)

[pcasaes]

This should fix it

#48643

Before the change the enabled check was performed before calling waitForTopicsToBeCreated
https://github.com/quarkusio/quarkus/pull/47863/files#diff-83fa96b2164c6e0483d856ee8064345b3776cd51dd951100fcd834abd5d8832cL128