Is your feature request related to a problem? Please describe.
There seems to be no easy way to list universal artifacts in a feed. Please add this functionality to the devops extension.
Describe the solution you'd like
az artifacts universal list --feed "<feed_name>" --version "*" --path "x/y/z"
The above command would list latest version of artifacts in "feed_name" at path "x/y/z"
You can list them thru the Web API - but you can't download
You can download them thru this extensions - but you can list them
Seems neither use case is actually useful... you'd have to combine them.
To get this straight, we are able to download a package using az artifacts universal download but we have no way of determining the existence of that package prior by using the same az cli tool.
Any update?
Thank you for sharing your feature request. We have taken this into our backlog for consideration. Unfortunately we cannot provide a timeline at this time, but we will consider this request as resources become available in the future.
@samuelkoppes seriously?!?
How do you expect a package system to be widely used in the field without having the option to list available packages?
Can you point me to any package system out there not offering this option?
I understand that the original request here is perhaps a bit complicated to implement.
But a more simpler version, without all the options mentioned by @praveen-pk, surfacing only the original Rest API is probably a low-hanging fruit you can integrate without much effort.
It will at least allows users having only the CLI to work more easily with the universal package product.
Any update? this would be a very handy feature.
In order to consolidate to fewer feedback channels, we've moved suggestions and issue reporting to Developer Community.
Most helpful comment
@samuelkoppes seriously?!?
How do you expect a package system to be widely used in the field without having the option to list available packages?
Can you point me to any package system out there not offering this option?
I understand that the original request here is perhaps a bit complicated to implement.
But a more simpler version, without all the options mentioned by @praveen-pk, surfacing only the original Rest API is probably a low-hanging fruit you can integrate without much effort.
It will at least allows users having only the CLI to work more easily with the universal package product.