-
Notifications
You must be signed in to change notification settings - Fork 7
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
Kafka Configuration Improvements #464
Comments
Hi, If I understood correctly you just want a different set of cluster setups right? You should be able to do it already as follows:
And then when creating subscriptions, simply refer to the cluster configuration using
|
@slinkydeveloper ah, so you can do it in the configuration file? It's un-documented, and I asked in the Discord and the response was that it had to be done in each individual subscription. Maybe it's just the documentation that needs updating then? |
Yep the
Yep you're right, looks like an area of our documentation that we need to improve, I'll sort this out :) |
Currently, a Kafka broker endpoint is configured in the configuration file, but if credentials are required then they need to be passed in as part of the
subscription
. Update this to allow credentials to be specified at the top level, keeping the subscription calls simple.Additional Context
I'd want to configure everything related to my Kafka connection at a higher level, in some kind of configuration. And then my subscriptions can stay exactly the same regardless of which server I'm connecting to
In the current model, if it works as you suggest, when I'm developing locally Vs when I'm deploying to a 'real' Kafka cluster I'd need to change all my subscriptions...
Whereas really I want to be able to switch my connection around (local, dev, prod etc) any the subscriptions 'just work'
Proposed Implementation
Update the
ingress.kafka-clusters.brokers
config option to take a struct instead of an array of strings. Allow the sasl.username and sasl.password to be specified as part of this config objectThe text was updated successfully, but these errors were encountered: