-
Notifications
You must be signed in to change notification settings - Fork 225
kafkasource: change bootstrapServers and Topics to accept arrays #1156
Conversation
Each item in the can be comma separated
/hold This change is not backward compatible. |
@lionelvillard right, I'm open to suggestions on how to do so -- but keeping in mind that the kafka api is Keep in mind that this change allows users to keep comma separated values in each element in the list, so it would be a minimal change. |
This will be backward incompatible change for kafka source in knative eventing. Not sure about how YAML parsing is done - is it possible to support both string and sequence of strings? |
I'd also not block this, due to the fact that kafka is early 🤷♂️ |
/unhold I'm fine with just having an Can you also open a doc issue to update the relevant Kafka examples? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Produced via:
prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github | grep -v docs/cmd/)
in knative/eventing-contrib#1156 we've updated the format for the topics and bootstrapServer to be lists, update example accordingly
@lionelvillard done, I've opened knative/docs#2410 to update the docs instead of filing an issue. Also updated the README.md in kafka's own source |
#2410) in knative/eventing-contrib#1156 we've updated the format for the topics and bootstrapServer to be lists, update example accordingly
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lberk, lionelvillard The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Each item in the list can be comma separated
Release Note
Action Required: KafkaSource now requires bootstrapServers and Topics to be in lists