Done
Details
Assignee
Ruslan LavrovRuslan LavrovReporter
Olamide KolawoleOlamide KolawolePriority
P2Story Points
5Sprint
NoneDevelopment Team
FolijetFix versions
Release
Poppy (R2 2023)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Ruslan Lavrov
Ruslan LavrovReporter
Olamide Kolawole
Olamide KolawolePriority
Story Points
5
Sprint
None
Development Team
Folijet
Fix versions
Release
Poppy (R2 2023)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 6, 2023 at 8:20 PM
Updated November 22, 2023 at 1:53 PM
Resolved September 26, 2023 at 8:01 AM
Purpose/Overview:
When Shared Instances are updated, Shadow Instances should be updated as well.
Requirements/Scope:
Shadow Instance should reflect the same HRID and other data points as the Shared Instance
Approach:
List to the inventory.instance kafka topic for updates to instances.
When a Shared Instance is updated -
get the locations of Shadow Instances from mod-consortia. This if from `/consortia/<consortiumId>/sharing/instances?query=sourceTenantId=college and instanceIdentifer=<UUID>`
Update the Shadow Instances at all locations returned by mod-consortia
Acceptance criteria:
Shadow Instance reflects updates to Shared Instance
Update time should be less than 3 seconds in a nominally operating cluster.
Covered by unit tests
Karate tests are created/updated
Module documentation updated
Logging is well-defined