So that applications can be deployed successfully consistently
I want to be able to ensure latest Kafka Topics configuration is on the broker at the point when I start my application during a deployment.
Therefore I want to be able to use within my application directly Kafka Configurator's KafkaAdminClient to do this. Presently it appears Kafka Configurator is published as a binary and not a JAR.
We have witnessed instances where deployments have failed due to Kafka Configurator having not been run (or possibly it has been run but other changes have run against Kafka Broker). My application should be able to safely create the topics it needs at run-time.
Considerations:
preventing deletion/destructive actions for existing topics;
ACLs re only changing your own applications topics (presumably intermediate and output topics)
So that applications can be deployed successfully consistently I want to be able to ensure latest Kafka Topics configuration is on the broker at the point when I start my application during a deployment.
Therefore I want to be able to use within my application directly Kafka Configurator's KafkaAdminClient to do this. Presently it appears Kafka Configurator is published as a binary and not a JAR.
We have witnessed instances where deployments have failed due to Kafka Configurator having not been run (or possibly it has been run but other changes have run against Kafka Broker). My application should be able to safely create the topics it needs at run-time.
Considerations: