-
Notifications
You must be signed in to change notification settings - Fork 238
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
request: jfrog rt s - allow to define include(<fields>) for aql search #320
Comments
This would be extremely helpful. Can you add this to your Spec File language? |
Resurrecting, since this would still be quite useful. |
would be useful |
It would be useful for me, also here is old stackoverflow question about that: |
Hi all, We've released a new version that would support this issue so now you can use --include that allows you to define specific fields for aql search. |
Hi, using Example:
Using following command:
Output:
|
I observed the same behavior as Opolonik using version 2.54.0. I also tried with --Include="name;repo;path;created_by" to no avail. |
even with v2.61.2 this problem persists if you set
you will see |
Does anyone have a work around for this? |
Hi.
It would be extremely helpful if it was possible to define include() for an aql search like possible through REST.
I want to define what field will be in the result JSON and not let jfrogcli decide this for me.
Thanks in advance!
The text was updated successfully, but these errors were encountered: