oscerd commented on issue #189: URL: https://github.com/apache/camel-kafka-connector/issues/189#issuecomment-6632303937
Sorry for the very late follow-up. The test harness can already run against an external broker: AbstractKafkaTest maps kafka.instance.type=remote (as well as local-kafka-container and local-strimzi-container) to a Connect worker that KafkaConnectRunnerService starts inside the test JVM, as described in the contributor testing guide (https://camel.apache.org/camel-kafka-connector/next/contributor-guide/testing.html). Pointing Kafka's EmbeddedConnectCluster at an external broker is still not possible with Kafka 4.2.1, whose builder only manages its own embedded brokers, and since that is internal Kafka test code, dropping the second runner would depend on an upstream change that nobody has pursued. Closing this as not planned; if maintaining both runners becomes a problem, please open a new issue. --- _Claude Code on behalf of Andrea Cosentino_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
