Draft: Expiring worker for access tokens refactored
What does this MR do and why?
Currently we have a single worker for expiring notification of access tokens. With this refactor, resource access token expiry worker is separated. This will help in eventual implementation of Web-hooks on the execution of resource access tokens.Also we can schedule two workers for a faster and parallel execution instead of one worker taking all load.
Relates to #426147 (closed)
MR acceptance checklist
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Edited by Smriti Garg