make oras-py behave the same way as oras-go for deciding whether to unpack a layer #170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #119
use the same logic as oras-go and cli for determining whether to unpack a tar layer or not.
With this implementation oras-py does not anymore use the layer's media type, it uses the annotation io.deis.oras.content.unpack.
that way artifacts published by oras-cli can be consumed the same way with oras-py and vice versa.
in addition, a skip_unpack param was added to the pull command in favor of #119