Uploaded image for project: 'mod-inventory-storage'
  1. mod-inventory-storage
  2. MODINVSTOR-738

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

    XMLWordPrintable

    Details

    • Template:
      Falcon user story template
    • Sprint:
      Prokopovych - Sprint 118, Prokopovych - Sprint 119, Prokopovych - Sprint 120
    • Story Points:
      3
    • Development Team:
      Prokopovych
    • Release:
      R2 2021 Bugfix
    • Hot Fix Approved by Cap Planning?:
      Yes
    • Hot Fix Approval Comments:
      Approved

      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. 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
            is blocked by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODRS-71 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
            is required by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODRS-71 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

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

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

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

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODINVSTOR-744 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

            Task - A task that needs to be done. MODINVSTOR-750 Release 21.0.2

            • TBD - To be determined
            • Closed
            mentioned in

            Page Loading...

              Activity

                People

                Assignee:
                marcjohnson Marc Johnson
                Reporter:
                mikhail.fokanov Mikhail Fokanov
                Votes:
                1 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases