Sajay Antony

Thinking more have we considered using --config-media-type and --artifact-type to disambiguate between them. This way there is no guess work on the CLI and the flags are mutually exclusive since...

With support for copy ORAS should handle container images as just another manifest with layers that needs to move. /cc @deitch

+1. I ran into this one as well. I think we need to target a v2 release of oras since this is breaking. Recommend renaming these to singular with multi...

Consider it you can just rename to annotations. Layer and config annotations are more coMplex scenario and so maybe if you wanted those we could use the —layer or —config...

I don’t think we need the config or layer in the CLI. Just discussing that it’s possible if and when the requirement comes, we have possibilities of opening up without...

I don't see the need for client APIs to mimic rest. But I do see the value in adding other fields from the descriptor into the ORAS output. Currently discover...

For releasing 1.0 having a clear idea of all exposed types have to be agreed upon. https://gist.githubusercontent.com/sajayantony/75bd90a7f3db4980b02b32bb6d23fd54/raw/e730fc31d6a87014f040f394289c904228af3601/diag.svg

I think given the number of request to show manifests - I've started a discussion here - https://github.com/oras-project/oras/discussions/340 /cc @mnltejaswini @shizhMSFT @deitch @jdolitsky

@qweeah - I will add more items to this issue as part of the migration to v2 and release of RC1.

/cc @michaelb990