Geo - Apply verification concurrency limit to all create/update events
requested to merge 443875-geo-create-and-update-events-should-not-immediately-enqueue-a-verification-job into master
What does this MR do and why?
For blobs and container repositories, instead of enqueuing a verification job immediately after every create or update event, this MR marks the registry as pending verification. This way, the verification will be slightly delayed, and the verification concurrency limit will control it. Both things will help reduce and control system load.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related issues
Related to #443875 (closed)
Edited by Douglas Barbosa Alexandre