Use events to refetch runners data
What does this MR do and why?
Pre-requisite of #352887 (closed)
This change refactors the way runner data is refetched when one of the runners is deleted.
Instead of using a global refetch in the mutation, each app is made responsible for refetching. This will give us more flexibility when responding to delete events.
Screenshots or screen recordings
No changes are expected, however once we delete a runner, it should be removed from the list:
How to set up and validate locally
- Visit admin runners http://gdk.test:3000/admin/runners
- Click on the X (delete) button for a runner
- Confirm the list is up to date after the deletion
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.
Related to #352887 (closed)
Edited by Miguel Rincon