[controller][server][clients] End-To-End support for SASL authentication with Kafka#452
Merged
ZacAttack merged 10 commits intolinkedin:mainfrom Jun 1, 2023
Merged
Conversation
- Fix Venice Server loading Kafka SASL parameters - Remove JAAS configuration from PulsarSink tests, Kafka is not configured with SASL - Add a generic `writerConfig` to tune the PulsarSink
Contributor
Author
|
All tests passed :-) |
FelixGV
approved these changes
May 29, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Ensure that SASL configuration is correctly propagated to all the components
Details:
How was this PR tested?
There is a new end-to-end test
Does this PR introduce any user-facing changes?