Add worker to sync scan result policies for a given project
What does this MR do and why?
During our work on MR !119792 (merged) we realized that we were introducing some duplicated code related to the sync policies process. This repeated code also caused performance issues in the past, as described here. We attempted to fix the performance issue in MR !116391 (closed). But back then, we opted for another solution to solve the performance issue.
To avoid code duplication and performance issues, this MR is bringing back the changes of MR!116391.
This MR introduces a new worker to sync scan result policies for a given project_id
.
Moving the sync process to a new worker makes sure we do not increase the latency of other services like the ones belonging to project authorizations domain.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.