Fix overwriting of low-level Kafka options with auth options #2
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.
Context
There was a problem with Kafka authorization due to the fact that the auth options overwritten the low-level kafka_config options. As a result, we could not use SASL_SSL authorization with an SSL certificate.
I fixed the line where the Kafka configuration was overwritten with the default authorization options. This looks more logical, and makes it possible to configure the connection to Kafka through the low-level config.
What's inside
uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger
error in thespec/rails_helper.rb
on older versions of Rails. Solution: Ensure the logger gem is loaded in Rails 7.0 rails/rails#54264 (comment)Failed job example: https://github.com/lxnewayfarer/sbmt-kafka_producer/actions/runs/12985571892/job/36210696308
Checklist: