Is your feature request related to a problem? Please describe.
I have an issue with creating a tag retention policies where rules is matching/excluding repositories alongside with nested repositories.
For example: Having two repositories projects/test and projects/repo/test2, creating a policies that match { test, repo/test2 } does not work. Dry run always stop. I even tried to replace / for %2F and %252F.
Describe the solution you'd like
I would like either
Fixing the issue, making it able to have repositories and nested repositories
An interface that will show all repositories with check boxes instead of writing it out
Adding an option to enable AND Logic
Describe the main design/architecture of your solution
A clear and concise description of what does your solution look like. Rich text and diagrams are preferred.
Describe the development plan you've considered
A clear and concise description of the plan to make the solution ready. It can include a development timeline, resource estimation, and other related things.
Additional context
My harbor version is in v2.10.0
Hello !
Is your feature request related to a problem? Please describe.
I have an issue with creating a tag retention policies where rules is matching/excluding repositories alongside with nested repositories. For example: Having two repositories projects/test and projects/repo/test2, creating a policies that match { test, repo/test2 } does not work. Dry run always stop. I even tried to replace / for %2F and %252F.
Describe the solution you'd like I would like either
Describe the main design/architecture of your solution A clear and concise description of what does your solution look like. Rich text and diagrams are preferred.
Describe the development plan you've considered A clear and concise description of the plan to make the solution ready. It can include a development timeline, resource estimation, and other related things.
Additional context My harbor version is in v2.10.0