Update user highest roles table
What does this MR do?
Part of #118592 (closed)
Whenever a Member of a Group or Project is added, updated or removed and the highest role for the Member's User changes a job will be schedule to update the user_highest_roles table.
The job will be scheduled 10 minutes into the future and outside of the Member's database transaction. It will also use an exclusive lease (30 minutes) and will only be scheduled if the job can take the lease. This is to avoid scheduling multiple jobs if the same action was triggered multiple times in a short period of time.
This is a suggestion from this comment in order to resolve performance issues when querying too much data.
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