Details
-
Story
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
Prokopovych - Sprint 118, Prokopovych - Sprint 119, Prokopovych - Sprint 120
-
3
-
Prokopovych
-
R2 2021 Bugfix
-
Yes
-
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:
- Topic name should be concatenated from the following string constants (in exactly the same order):
- Environment name (from ENV environment variable)
- Tenant name (should be the second, because it is convenient to use wildcard in ACL for Kafka users)
- Producer module name ("storage" postfix should be omitted)
- 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
-
MODRS-76
R1 Hotfix -> R2 Bugfix - Kafka Topics should use ENV variable and tenant id in their naming convention
-
- Closed
-
- is blocked by
-
MODRS-71
Kafka Topics should use ENV variable and tenant id in their naming convention
-
- Closed
-
- is required by
-
MODRS-71
Kafka Topics should use ENV variable and tenant id in their naming convention
-
- Closed
-
-
MSEARCH-132
Kafka Topics to use ENV variable and tenant id in their naming convention
-
- Closed
-
-
MSEARCH-154
Kafka Topics to use ENV variable and tenant id in their naming convention
-
- Closed
-
- relates to
-
MODINVSTOR-744
Kafka Topics should use ENV variable and tenant id in their naming convention
-
- Closed
-
-
MODINVSTOR-750 Release 21.0.2
-
- Closed
-
- mentioned in
-
Page Loading...