Repository navigation
backend: bump franz-go version to support custom aws msk dns names - #2452
Merged
Merged
Conversation
weeco
approved these changes
May 19, 2026
weeco
enabled auto-merge (rebase)
May 19, 2026 08:15
# Conflicts: # backend/go.mod # backend/go.sum
auto-merge was automatically disabled
May 20, 2026 11:27
Rebase failed
themkarimi
pushed a commit
to themkarimi/console
that referenced
this pull request
Jun 19, 2026
…edpanda-data#2452) Co-authored-by: Julin <142230457+c-julin@users.noreply.github.com>
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
3 participants
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.
Hey,
currently custom AWS MSK DNS names are not supported, as franz-go before 1.21.2 tried to extract the AWS region out of the DNS name. However, the AWS region is not part of a custom DNS url for the MSK cluster. franz-go 1.21.2 support's the extraction of the region from env var's in case no region is found in the url, see the changelog