Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added a custom SASL config option to the Topic Operator #5473 #9606
Added a custom SASL config option to the Topic Operator #5473 #9606
Changes from 98 commits
a07507f
b8bbe5f
8faa578
3a50659
cce0581
68c576e
79427ab
5ba77f5
e9f237d
a2431bc
cdbb681
b2458fb
50b1a03
0cb145c
5c1605c
8d0de96
b03be6d
615517a
c3b4fc0
fbe94d1
a4d5a55
83b0895
de23ad1
c2e5682
6dca372
52b045f
c806183
a22e38b
bd777a5
01c078d
fa2742b
7e56d0c
5a800b4
421b58e
7be96f3
1aa3155
c05aa45
d7efe95
e7d5b72
2a9a4cd
b305f93
4753583
7af6b08
9e158ee
3d742cb
64920f6
bca3593
b0f9beb
445b014
9f97fc4
55547c8
3fbebcc
5321b04
a2d7d11
ca05d36
3f2c8fc
4516a23
91521b1
9607ce5
51a5676
626f8ea
98f69cc
30d43c9
ebb1d76
2ab4b82
b3bcbef
5fd072a
abab6c7
cac01a5
59c59ca
f2e3727
19eb604
5ed5401
a9fa314
9ef2abb
a76df7b
890f2c7
a87c3cf
bb59d8c
255b2a5
1e7bd12
49bcfce
7360541
0d63ccf
e1a2fde
86b1438
f5832d9
fef4ded
d1fc94b
4a5f20d
5a5c107
bd0b250
5942024
37632f3
149cb17
299f2d9
9b6a206
9794bc4
1f151cc
da51009
98918ff
b3fb404
3a6afea
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
despite there is an ignore case, you are mentioning "none" (lower case) here but "NONE" (upper case) in the previous doc. I would stick with the same on both, i.e. "none" lower case.
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.
right, let's keep them aligned
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.
Ok, so, "none" everywhere including the documentation?
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.
I would say yes
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.
What do we do for other similar options? Didn't @fvaleri before suggest to use uppercase? This should be also consistent with the
ALL
I guess?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.
I am just for consistency so even the upper case is fine with me.
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.
Guys, I just need an answer. Upper or lower? Please.
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.
@john-mcpeek Well, it makes no sense to have
none
andALL
. So one way or another there will be another change needed. It was actually @tombentley who suggested upper case in #9606 (comment) and I think his logic makes sense. So if Paolo doesn't care you should go with uppercase everywhere.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.
Tom originally suggested to have all uppercase as it is more evident comparing to regular configuration, which is lowercase. So let's use UPPERCASE (NONE and ALL).
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.
Ok, I think we are NONE and ALL everywhere now.
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.
again despite the ignore case, why are you using "NONE" here instead of "none" as before? I would make consistency everywhere, even across the documentation part.