set ssl.endpoint.identification.algorithm to null
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Hello, 1st I want to congratulate the team for this tool... is great... now to my concern. I want to monitor a consumer I have in Heroku Kafka and while I saw from rather an issue that the dependency on Zookeeper can be worked around (by setting a local one) but the next I issue I need to fix is how to set up the value of "**ssl.endpoint.identification.algorithm**" to null.. by default is https. but heroku among other SSL clusters providers, require a null value. Can this be achieved with Burrow?
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating Burrow’s Kafka consumer configuration and its TLS option handling, then trace how ssl.endpoint.identification.algorithm is represented and passed through. Done means a Burrow configuration can set it to null and connect to Heroku Kafka without the default HTTPS identification behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- security, stream-processing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100