Uploaded image for project: 'mod-remote-storage'
  1. mod-remote-storage
  2. MODRS-71

Kafka Topics should use ENV variable and tenant id in their naming convention

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P2
    • Resolution: Done
    • None
    • 1.0.6, 1.4.0
    • None
    • Firebird Sprint 118
    • 2
    • Firebird
    • R1 2021 Hot Fix #3
    • Yes

    Description

      Purpose/Overview:

      ENV and tenant id setting should be used in topic naming convention. This will separate data of different customers to different Kafka topics. In addition to that it allows a Kafka instance to be shared by multiple environments that have the same tenant id. 

       

      Requirements/Scope:

      1. Topic name should be concatenated from the following string constants (in exactly the same order):
        1. Environment name (from ENV environment variable)
        2. Tenant name (should be the second, because it is convenient to use wildcard in ACL for Kafka users)
        3. Producer module name ("storage" postfix should be omitted)
        4. Domain entity name in singular form (if it is not domain event, the name of process should be used or just event name)

      Acceptance criteria:

      All existing topics should be aligned.

      For example topics in bugfest (ENV  == bugfest) the Kafka topic for inventory instances for tenant fs09000000 should have the following name:

      bugfest.fs09000000.inventory.instance

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-738 Kafka Topics should use ENV variable and tenant id in their naming convention

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODRS-72 Improve logging: Accession flow for Dematic doesn't work

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. MODRS-75 MODRS (mod-remote-storage) Hotfix release

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            defines

            New Feature - New feature requests UXPROD-2854 Firebird - R2 Enhancements/Bugfixes/Tech Debt

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            is cloned by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODRS-76 R1 Hotfix -> R2 Bugfix - Kafka Topics should use ENV variable and tenant id in their naming convention

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            requires

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-738 Kafka Topics should use ENV variable and tenant id in their naming convention

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Activity

              People

                khandramai Viachaslau Khandramai
                mikhail.fokanov Mikhail Fokanov
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases