Kafka functions: structured configuration in func.yaml (optional)
- Dominant language
- Go
- Stars
- 365
- Forks
- 223
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 25
Description
Kafka connection is currently configured via plain environment variables (`KAFKA_BROKERS`, `KAFKA_TOPICS`, `KAFKA_CONSUMER_GROUP`). An alternative would be a structured `middleware.kafka` section in `func.yaml` for brokers, topics, consumer group, and auth settings. The CLI would translate this into environment variables at build/deploy time.
This may not be necessary — env vars work well and are already supported via `func config envs add` with plain values, Secrets, and ConfigMaps. A structured config section would add convenience but also complexity. Needs discussion on whether the value justifies the cost.
Contributor guide
Research direction
Start by reviewing the existing Kafka environment-variable support and how func config envs add handles plain values, Secrets, and ConfigMaps. Discuss whether a middleware.kafka section in func.yaml would justify the added complexity; done means a maintainer decision on whether to pursue the structured configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100