Open ajesk opened 2 months ago
Hi ajesk! 👋
Welcome, and thank you for opening your first issue in the repo!
Please wait for triaging by our maintainers.
As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues. Sponsorship link
If you plan to raise a PR for this issue, please take a look at our contributing guide.
Hi @ajesk, I suggest that a pattern check ignoring the case is preferred here as it won't introduce breaking changes. Feel free to submit a PR!
Hello! Sorry, can we use regex for topic name in protobufMessageNameByTopic
?
There are regex patterns already in place. I performed work removing them because they were just being used as a strict less performant equals alternative.
If this isn't ideal I can just leave them there and append a case insensitive check.
On Mon, Sep 16, 2024, 18:29 luckyrider @.***> wrote:
Hello! Sorry, can we use regex for topic name in protobufMessageNameByTopic?
— Reply to this email directly, view it on GitHub https://github.com/kafbat/kafka-ui/issues/538#issuecomment-2354140712, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADAGTVPRP4YFBRWSCZYP5ETZW5LVZAVCNFSM6AAAAABNZS2RS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJUGE2DANZRGI . You are receiving this because you were assigned.Message ID: @.***>
Issue submitter TODO list
main
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
When using environment variables to configure kafka-ui. There is a case sensitivity issue with how the topic/proto key value pairs are generated. I know that this is not the preferred way for configuring the service, but it is the most accessible way to configure when using Kubernetes.
Using an example from the documentation
becomes
In this case the topics both lose their casing. Within the code, it seems that there are no case sensitivity checks that occur so the topics included will never have access to the protos that should be assigned.
Writing
Reading
Expected behavior
Either the configuration structure needs to be slightly modified to support storing the case sensitive topics.
Or adjust the pattern checks to ignore casing.
Your installation details
Kubernetes. Not completely applicable
Steps to reproduce
Configure protofile serdes via env variables with lowercase topic names. See that the protofiles are not accessible to the topic.
Screenshots
No response
Logs
No response
Additional context
If this seems like a reasonable fix, I am willing to make the adjustments in the preferred manner.