Fix KafkaContainer with multiple networks defined #4213
Merged
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.
Current implementation exposes only two listeners PLAINTEXT and BROKER.
BROKER must be advertised to the explicitly specified network or bridge.
When a host port is exposed using Testcontainers.exposeHostPorts and a network is specified, the current implementation iterates through both network (specified and proxy container), incorrectly creating two listener with the same name "BROKER"