question: Would you consider this enhancement? about go-containerregistry HOT 3 OPEN

That seems useful, yeah.

I wonder if a --header flag would be useful at the root command, so that every command gets it "for free" instead of having to add it to each command individually. This would mean things like crane pull, crane mutate, crane export would also be able to be configured to send headers.

from go-containerregistry.

I defer to the maintainers. My purpose for the new flag is to drive a pull through registry. In order to test it - the pull through registry needs to honor the header so - that makes it tough to test unless I also signed up to modify the pkg/registry code to implement pull-through using the header which is a substantial bit of work I would think...

from go-containerregistry.

Actually - containerd appends ?ns= as a query parameter when mirroring is configured. So maybe rather than a header, the various REST API calls could have the namespace appended just like containerd does... Then crane would be behaving identically to containerd. In that case the arg would be something other than --header

from go-containerregistry.