Add --dry-run option to registry-garbage-collect command.
What does this MR do?
Currently the only way to execute a dry run container garbage collect is to run the command directly against /opt/gitlab/embedded/bin/registry
. This change extends the existing gitlab-ctl registry-garbage-collect
command to support the --dry-run option.
Related issues
None
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Edited by Robert Marshall