Stop stripping curly braces from tag retention policies #20806
Comments
It seems that the Harbor UI does indeed remove the first and the last curly braces from the tag retention policy, while the http request payload sent to the backend API does contains a valid tag patten. And it does select the artifacts matching the tag patten. Please check the above attached images. |
|
It is a by design behavior. |
|
Hi @sebhoss , Thanks for reaching out to us and we are aware that this design would made some confusion at your side. Since initially we are trying to simplify this Let's keep collecting the feedback from community! Best, |
|
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
I'm trying to implement a somewhat semver compatible tag retention policy. I've tried the one from #12877 (comment) but removed the
vin front since our versions do not use such a prefix. The Harbor UI then stripped the curly braces in front and end of the expression.Steps to reproduce the problem:
{[0-9],[0-9][0-9],[0-9][0-9][0-9],[0-9][0-9][0-9][0-9]}.{[0-9],[0-9][0-9],[0-9][0-9][0-9],[0-9][0-9][0-9][0-9]}.{[0-9],[0-9][0-9],[0-9][0-9][0-9],[0-9][0-9][0-9][0-9]}into tag retention UIVersions:
Please specify the versions of following systems.
Additional context:
harbor.ymland files in the same directory, including subdirectory./var/log/harbor/.The text was updated successfully, but these errors were encountered: