[elixir] feat: Extend Fluss.Config with security, SASL and connect timeout options#577
Merged
fresh-borzoni merged 2 commits intoMay 28, 2026
Merged
Conversation
This commit adds 5 fields to NifConfig: connect timeout ms and security_* settings (protocol, sasl mechanism, usernama and password)
This commit adds 5 fields to Fluss.Config with the corresponding setters: connect timeout, security protocol, sasl mechanism, username and password. To ensure that the password is redacted, we add a custom Inspect impl, essentially mirroring the upstream rust debug redaction.
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.
Purpose
Linked issue: close #569 and the parent #463.
Brief change log
This PR follows up on #574 to extend Fluss.Config with configuration options for security protocol, SASL and connect timeout. To ensure that the SASL password, if set, gets redacted in logs, we customise how Fluss.Config gets inspected using the Inspect protocol; it would appear as
[REDACTED]in logs.We otherwise follow the same approach as in the related PRs.
Tests
New tests cover the setters that were added for these options, one for each function.