Is your feature request related to a problem? Please describe.
I want to exclude images in a specific repo from being replicated, while all other images can be replicated as usual. However:
Name doesn't support excluding.
We cannot change Tag as we use its format for other purpose.
Excluding Label doesn't work as expected: it seems I have to push the image first and then add a label to the image. But before I add a label, the image push event already triggers a replication task and starts the replication.
I'm using push-based, event-based replication.
Describe the solution you'd like
Support excluding Name in replication source filter. (ideally)
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
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
I want to exclude images in a specific repo from being replicated, while all other images can be replicated as usual. However:
Name
doesn't supportexcluding
.Tag
as we use its format for other purpose.Label
doesn't work as expected: it seems I have to push the image first and then add a label to the image. But before I add a label, the image push event already triggers a replication task and starts the replication.I'm using push-based, event-based replication.
Describe the solution you'd like
excluding Name
in replication source filter. (ideally)excluding Label
work in push-based, event-based replication. (as suggested in https://github.com/goharbor/harbor/issues/20253#issuecomment-2054062267, which doesn't quite work in my experiment).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 Add any other context or screenshots about the feature request here.