Uploaded image for project: 'Sentry (Retired)'
  1. Sentry (Retired)
  2. SENTRY-2177

Allow suffix wildcards for Kafka topic management

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: kafka-integration, Sentry
    • Labels:
      None
    • Docs Text:
      Hide
      Applications using Kafka Streams rely on being able to create internal topics as part of their workflow - https://docs.confluent.io/current/streams/developer-guide/manage-topics.html#streams-developer-guide-topics-internal

      Currently this means admin access needs to be granted to the application user to manage topics. Allowing prefix + wildcard for topic resources would allow applications to manage and access a subset of topics based on name e.g.

      Host=127.0.0.1->Cluster=kafka-cluster->action=create->prefix=application.id
      Host=127.0.0.1->Topic=application.id*->action=write
      Show
      Applications using Kafka Streams rely on being able to create internal topics as part of their workflow - https://docs.confluent.io/current/streams/developer-guide/manage-topics.html#streams-developer-guide-topics-internal Currently this means admin access needs to be granted to the application user to manage topics. Allowing prefix + wildcard for topic resources would allow applications to manage and access a subset of topics based on name e.g. Host=127.0.0.1->Cluster=kafka-cluster->action=create->prefix=application.id Host=127.0.0.1->Topic=application.id*->action=write

      Attachments

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            jimhalfpenny Jim Halfpenny
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: