-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 ServiceName hard-coded instead of a config metadata item #5474
Comments
Hey, |
2 tasks
I asked my coworker if he could help take it on. I believe he raised a pull
request already. I will ask him to post it here for reference.
Thank you.
…On Sat, Feb 3, 2024, 5:22 AM Jorge Turrado Ferrero ***@***.***> wrote:
Hey,
For sure! Are you willing to open a PR with the support for it?
—
Reply to this email directly, view it on GitHub
<#5474 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APSJRK2I2VVXRLY6KDCYV5DYRY23DAVCNFSM6AAAAABCW5BDNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVGMZDANRSGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Merged
1 task
github-project-automation
bot
moved this from To Triage
to Ready To Ship
in Roadmap - KEDA Core
Mar 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our enterprise kafka implementation uses a different service name in each environment. Can the ServiceName be a metadata config item like so many of the other items instead of hardcoded?
keda/pkg/scalers/kafka_scaler.go
Line 544 in 6d326c8
The text was updated successfully, but these errors were encountered: