Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.8.0
-
None
Description
With more and more components relying on sentry for authorization, it really makes sense to have the case-sensitivity configurable. We can keep the current behavior as default. However, for use cases like Kafka, it makes sense to have authorizable names case sensitive. For instance, a topic resource in Kafka can have case sensitive values, like, topic1 and TOPIC1 are two completely different valid topic resource instances.
Attachments
Attachments
Issue Links
- blocks
-
SENTRY-912 Sentry integration with Apache Kafka
- Resolved
- links to