Use AuthorizedProjectRefresh::ProjectCreateWorker for project create
What does this MR do?
AuthorizedProjectRefresh::ProjectCreateWorker
as a specialized worker use much less resource to update project authorizations but it could lead to synchronization issues because it doesn't serialize simultaneous update events. The previous approach of AuthorizedProjectsWorker
is not bulletproof either, inconsistencies do accumulate in the project authorization cache over time. For now, we also use the previous approach as a safety measure but with some delay and lower priority (AuthorizedProjectUpdate::UserRefreshWithLowUrgencyWorker
).
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Imre Farkas