Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replication filter - exclude by name #20253

Open
Aransh opened this issue Apr 9, 2024 · 2 comments
Open

Replication filter - exclude by name #20253

Aransh opened this issue Apr 9, 2024 · 2 comments
Assignees
Labels
area/replication kind/requirement New feature or idea on top of harbor

Comments

@Aransh
Copy link

Aransh commented Apr 9, 2024

Is your feature request related to a problem? Please describe.
Yes, I am having issues with replicating from Azure ACR source.
In the replication logs, I can see that all failing artifacts are of type jar (Resource type appears as image, but the actual resource is a jar) which is of course not supported by Harbor.

Describe the solution you'd like
Since all failing artifacts names seem to start with "jar/", I figured I'd add a filter to exclude "jar/**", but appears Harbor doesn't support exclusion by name (while it does support exclusion by label/tag, which I do not have on these artifacts)

Describe the main design/architecture of your solution
Same as tag/label implementation, add selector for "includes/excludes" when setting name filter

Additional context
Another possible solution is for Harbor to identify these are jars (instead of how it currently identifies them as images) and ignore.
I wasn't even aware ACR allows storing Jars, but turns out our dev team uses this feature for Azure databricks, which is not relevant for my Harbor environment.

@wy65701436 wy65701436 added area/replication kind/requirement New feature or idea on top of harbor labels Apr 11, 2024
@zyyw
Copy link
Contributor

zyyw commented Apr 14, 2024

One workaround to this issue might be to label the set of artifact you want to exclude with a label name, and utilizing the matching/excluding label feature. Or given them a specific pattern of tag and utilizing the matching/excluding tag feature.

@Aransh
Copy link
Author

Aransh commented Apr 15, 2024

@zyyw That's problematic for me as I have no control of these artifacts, I just need to replicate them with no modification to the origin repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/replication kind/requirement New feature or idea on top of harbor
Projects
None yet
Development

No branches or pull requests

4 participants