Due to eventual consistency we have issues with duplicated course events. It happens because the old events could not be properly deleted from the course by eventId. To prevent this situation in the future a new route was introduces which deletes all events for scopeId = courseId.
In addition to that in the database there are already multiple duplicated events which should be cleaned up from there by migration. For this case additional route for deletion of the duplicated events was introduced.
As duplicated event is considered an event which was created before 20 seconds before maximal last modification date of the corresponding course.
Description
Due to eventual consistency we have issues with duplicated course events. It happens because the old events could not be properly deleted from the course by eventId. To prevent this situation in the future a new route was introduces which deletes all events for scopeId = courseId.
In addition to that in the database there are already multiple duplicated events which should be cleaned up from there by migration. For this case additional route for deletion of the duplicated events was introduced. As duplicated event is considered an event which was created before 20 seconds before maximal last modification date of the corresponding course.
Links to Tickets or other pull requests
Changes
Datasecurity details on Confluence
Deployment
New Repos, NPM pakages or vendor scripts
Screenshots of UI changes
Approval for review
Link to Definiton of Done
More and detailed information on the definition of done can be found on Confluence