Is your feature request related to a problem? Please describe.
zarf tools registry is currently an alias for the Crane CLI. The Crane CLI often has trouble with non container images, during pull for instance, it treats every layer of an image as a tar file, even though many OCI images have non tar layers now.
This will give us more flexibility to add functionality to commands. For instance we could make a new command or add a flag to zarf tools registry pull which would pull layers by annotations similar to oras pull.
Most commands would be rather simple to implement, for instance we already have functionality in Zarf to pull and push images, and oras-go can be leaned on for other commands.
We should remove the alias zarf tools registry Crane
zarf tools registry export would be hard to duplicate, I also consider it in the domain of working with container images rather than working with a registry, and so I believe it would be out of scope and should be deprecated / removed in v1
Alternatives
We could use the oras CLI, but then we are beholden to another tool, and I find the UX of ORAS CLI to be confusing at times.
Is your feature request related to a problem? Please describe.
zarf tools registryis currently an alias for the Crane CLI. The Crane CLI often has trouble with non container images, during pull for instance, it treats every layer of an image as a tar file, even though many OCI images have non tar layers now.This will give us more flexibility to add functionality to commands. For instance we could make a new command or add a flag to
zarf tools registry pullwhich would pull layers by annotations similar tooras pull.Most commands would be rather simple to implement, for instance we already have functionality in Zarf to pull and push images, and oras-go can be leaned on for other commands.
We should remove the alias
zarf tools registry Cranezarf tools registry exportwould be hard to duplicate, I also consider it in the domain of working with container images rather than working with a registry, and so I believe it would be out of scope and should be deprecated / removed in v1Alternatives
We could use the oras CLI, but then we are beholden to another tool, and I find the UX of ORAS CLI to be confusing at times.