Uppercase Letters in cluster name gives error in consumers

Burrow has issues reading the consumers from a cluster with uppercase letters in the name. The cluster is recognized, including the topics but when the consumer endpoints is hit, it returns an empty array.
While this happens, burrow outputs warn level logs as follow
`{
"level": "warn",
"ts": 1573072830.5585341,
"msg": "unknown cluster",
"type": "module",
"coordinator": "storage",
"class": "inmemory",
"name": "default",
"worker": 6,
"cluster": "Module-Core-Kafka-Cluster",
"consumer": "claims-intake-java",
"topic": "test-topic",
"partition": 27,
"topic_partition_count": 0,
"offset": 8741,
"timestamp": 1573072830000,
"owner": "",
"client_id": "",
"request": "StorageSetConsumerOffset"
}`
That consumer should be in the correct cluster but it shows as unknown. This does not happen when the cluster's name is fully lower case. I need to set burrow in production and the cluster name can not be changed as I am using Amazon MSK.
If it has a workaround apart from changing the name, please help me out. Or it has to get fixed

Reproduce the consumer-endpoint failure with an uppercase cluster name and inspect the code path that emits the "unknown cluster" warning. Trace how cluster names are matched between topic and consumer data; done means the expected consumer is returned for uppercase names without the warning.

Written by the indexing model from the issue text.