Arvados

If you manually upload an image with arv-keepdocker, you almost certainly want the portable data hash to put in a container request or workflow that you're writing. But as far as I can tell the tool will never show you this.

We should look at what scripting we currently have around arv-keepdocker to see how many tools, if any, are relying on the current output. This isn't definitive but suggestive. Suggest git grep "keep.?docker". Also search our Jenkins scripts.

I think we should add a switch --collection-id=<uuid|portable_data_hash|pdh> that determines what gets output. It is effective both after an upload and in the listing output.

If you upload without specifying this option, what should the output be? If there are no major backwards compatibility concerns, I'd argue it should output both. What format? Space-separated, line-separated, JSON, something else?

Listings should default to portable data hash IMO, and you can specify --collection-id=uuid to get the current output.