chore: write kcat configuration to a kcat.conf file instead of using them inline

Open
#779 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
kafka, rust
Domain
cli

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.

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.

Dominant language
Rust
Stars
28
Forks
8
Avg merge
2d 12h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/kafka-operator

All issues in stackabletech/kafka-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.