Skip to content

Project Search Should support query #355

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

Open
Vad1mo opened this issue Mar 18, 2025 · 3 comments
Open

Project Search Should support query #355

Vad1mo opened this issue Mar 18, 2025 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@Vad1mo
Copy link
Member

Vad1mo commented Mar 18, 2025

Searching should support the capabilities of Harbor:

string(query) Query string to query resources. Supported query patterns are "exact match(k=v)", "fuzzy match(k=v)", "range(k=[minmax])", "list with union releationship(k={v1 v2 v3})" and "list with intersetion relationship(k=(v1 v2 v3))". The value of range and list can be string(enclosed by " or '), integer or time(in format "2020-04-09 02:36:00"). All of these query patterns should be put in the query string "q=xxx" and splitted by ",". e.g. q=k1=v1,k2=v2,k3=[minmax]
@rizul2108
Copy link
Collaborator

@bupd The query flag is currently in the project list command, but the logic for handling it has not been implemented yet. Additionally, it is not included in the project search command. Would it be appropriate to move the query flag to the project search command and implement the logic there?

@bupd bupd assigned bupd and rizul2108 and unassigned bupd Apr 21, 2025
@bupd bupd added the enhancement New feature or request label Apr 21, 2025
@rizul2108
Copy link
Collaborator

query flag should be added to project search or list as currently in harbor api it is in list command parameters not in search

@rizul2108
Copy link
Collaborator

@bupd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants