Project List should support query

[Vad1mo]

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]

@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?

[rizul2108]

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]

@bupd

[NucleoFusion]

Is there work being done on this? I would like to work on it.

[bupd]

@NucleoFusion please do share your plan and your overall understanding in the issue before creating a PR

[NucleoFusion]

@bupd Okay let me have a detailed look on the issue and code, and think for a little. Then Ill get back to you

[NucleoFusion]

@bupd Okay, so I took a look at the code and the API docs (go code).

Query string to query resources. Supported query patterns are "exact match(k=v)", "fuzzy match(k=~v)", "range(k=[min~max])", "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=[min~max]

From this comment on the param I can gather that there would be 3 different ways to use the query string, exact match, fuzzy match, and range.

The format required by the SDK is "name=library,id=2".

I am thinking, instead of having one --query flag
we have --match, --fuzzy and --range.

So a command like
harbor project list --fuzzy name=lib --match access_level=public --range id=1~10
would translate to
name=~lib,access_level=public,id=[1~10]

We could also add type checking and error handing, that is checking if the key matches ID/Project Name/Access Level etc
So something like nme=lib would produce error and tell the user that nme is not a key.

What do you think? Shall I start working on it?