Brian Goff e037bade8c Use ocischema package instead of custom handler ... Previously we were re-using schema2.DeserializedManifest to handle oci manifests. The issue lies in the fact that distribution started validating the media type string during json deserialization. This change broke our usage of that type. Instead distribution now provides direct support for oci schemas, so use that instead of our custom handlers. Signed-off-by: Brian Goff <cpuguy83@gmail.com> (cherry picked from commit e443512ce4) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>		2019-10-14 23:06:05 +02:00
..
fixtures/validate_manifest
metadata
utils
xfer
config.go
errors.go
errors_test.go
pull.go	Remove v1 manifest code	2019-06-18 18:54:59 +00:00
pull_v2.go	Use ocischema package instead of custom handler	2019-10-14 23:06:05 +02:00
pull_v2_test.go
pull_v2_unix.go
pull_v2_windows.go
push.go	Remove v1 manifest code	2019-06-18 18:54:59 +00:00
push_v2.go	distribution: modify warning logic when pulling v2 schema1 manifests	2019-09-19 00:46:14 +00:00
push_v2_test.go
registry.go	distribution: modify warning logic when pulling v2 schema1 manifests	2019-09-19 00:46:14 +00:00
registry_unit_test.go