-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
fix: populate env.json with valid Kafka bootstrap addresses #188
Conversation
The generator was putting the "kafka-secure://" protocol prefix in the bootstrap address for generated Kafka apps, which the Kafka client library rejects as an invalid URL. This commit uses the hostname if it is available (v3 docs) but falls back to using the url otherwise (v2 docs). Signed-off-by: Dale Lane <dale.lane@uk.ibm.com>
/rtm |
Hello, @dalelane! 👋🏼 |
/rtm /au |
Hello, @dalelane! 👋🏼 |
Please retry analysis of this Pull-Request directly on SonarCloud |
Quality Gate passedIssues Measures |
/rtm |
🎉 This PR is included in version 0.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
The generator was putting the "kafka-secure://" protocol prefix in the bootstrap address for generated Kafka apps, which the Kafka client library rejects as an invalid URL.
This commit uses the hostname if it is available (v3 docs) but falls back to using the url otherwise (v2 docs).