Skip to content

Adding resources filtering logic for delete task

Tiffany Rea requested to merge add-filters-for-resource-delete-task into master

What does this MR do and why?

Describe in detail what your merge request does and why.

Accommodating changes in !78587 (merged) but is not a dependency of said MR.

!78587 (merged) removed filtering logic from collect method so it can collect all resources. Moving filtering logic into delete task instead.

For more context, we will be calling this task in a job in a later stage after test stage has finished (For example, in Staging gitlab-org/quality/staging!80 (merged)). So after each test job finishes, it would produce a JSON file like this https://gitlab-org.gitlab.io/-/gitlab-qa-mirror/-/jobs/2003171546/artifacts/gitlab-qa-run-2022-01-21-20-21-03-a701d035/gitlab-ee-qa-2a64473e/test-resources-be3469.json. This task would read this file, filter out what can be deleted and perform deletion. For starter, we are just going to print what failed to be deleted to the console. I planned to do a retry in a later iteration.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Tiffany Rea

Merge request reports