stackabletech / stackabletech/kafka-operator
chore: write kcat configuration to a kcat.conf file instead of using them inline
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 28
- Forks
- 8
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 9
Description
If these configuration options are written to a kcat.conf file instead of creating command line parameters, it makes it much easier to use kcat for debugging purposes.
See https://github.com/stackabletech/kafka-operator/pull/762#discussion_r1800731210.
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
Start with the discussion linked from PR 762, then locate where kcat configuration is assembled as inline command-line parameters. Update the relevant configuration flow to use a kcat.conf file instead, and verify that the generated configuration supports the debugging use case described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, rust
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100