-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Priming kafka-manager with 'zkhosts' of a known set of kafka clusters #37
Comments
We may be able to introduce a way to make the kafka manager "read-only" in terms of adding/modifying/deleting clusters. And for bootstrap, we can just bundle a CLI utility which you can use to define a new cluster. |
I would like a way to specify the clusters in the application.conf as well. It would also be nice to have a read only option too. |
I believe this effort has started inh ttps://github.com/yahoo/kafka-manager/commit/18d370dd60896100927dc17ced766bd358b56645 and has been getting updates as needed. |
Hi,
We want to automate some of the kafka management by
To achieve this, we also need to be able to prime (pre-populate) a kafka-manager instance with a set of kafka clusters' 'zkhost' lists. We intend to provide the list via the application conf (As a list of lists) and set that value in the conf during puppet install of the kafka-manager.
But I am struggling a bit to find a nice 'bootstrap' (Startup) point in the lifecycle of the kafka-manager app to insert a populate_kafka_clusters() method. May be because I am very new to Scala and Play. Can you please point me to such a location or if there is none, can it be added so that other such initializations can be added by others at that interception point? Also can you point me to the code that takes the 'zkhosts' for a cluster and adds them to the backend store (kafka-manager's Zookeeper namespace /kafka-manager I presume)
The text was updated successfully, but these errors were encountered: