-
Notifications
You must be signed in to change notification settings - Fork 53
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
brod
supports sasl credentials from file
#135
Conversation
`brod` supports having credentials in a file (which is good since they do not stay in the producer state and they are not exposed upon inspection). https://github.com/kafka4beam/brod/blob/master/README.md?plain=1#L425-L428
I'll squash commits before merging if the PR is accepted, since we are pointing to my branch HEAD in our systems at the moment. |
|
||
defp validate_option(:sasl, {mechanism, path} = value) | ||
when mechanism in [:plain, :scram_sha_256, :scram_sha_512] and | ||
is_binary(path) do |
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.
To they actually allow the path to be a binary or must it be an Erlang string (i.e. Elixir charlist?)?
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.
We have it working as binary, I'm not sure if it allows a charlist, do you want me to check? I'm following the same typing approach as the existing username/password
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.
If it works as a binary, that's all we need.
@rewritten please update the tests too :) |
💚 💙 💜 💛 ❤️ |
@rewritten: Nice! Linked to: |
Hi folks! This PR adds support for file-based sasl credentials. From
brod
readme (https://github.com/kafka4beam/brod/blob/master/README.md?plain=1#L425-L428) (emphasis mine):