You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice if flux pull artifact supported layer selection in the same way OCIRepository does.
More generally, I do wonder if there is a way to improve make CLI feature parity for some cases like this. It would seem useful to be able to run flux pull with any source object definition and extract it to a dir, respecting all object fields. It might be tricky to handle credentials, but surely not unsolvable, perhaps any secret refs would just have to be passed as flags or env vars, if reading from a cluster is not an option.
Of course, when it comes to git, most people are familiar with git clone, however, OCI poses a very specific challenge, one has to understand OCI to make good use of crane (as the first example that comes to mind), I don't know if oras might be a bit easier...
The text was updated successfully, but these errors were encountered:
It would be really nice if
flux pull artifact
supported layer selection in the same wayOCIRepository
does.More generally, I do wonder if there is a way to improve make CLI feature parity for some cases like this. It would seem useful to be able to run
flux pull
with any source object definition and extract it to a dir, respecting all object fields. It might be tricky to handle credentials, but surely not unsolvable, perhaps any secret refs would just have to be passed as flags or env vars, if reading from a cluster is not an option.Of course, when it comes to git, most people are familiar with
git clone
, however, OCI poses a very specific challenge, one has to understand OCI to make good use ofcrane
(as the first example that comes to mind), I don't know iforas
might be a bit easier...The text was updated successfully, but these errors were encountered: