add artifact_type for artifact model to support artifactType filter
Signed-off-by: yminer <yminer@vmware.com>
add 2.11 sql schema & update index artifactType omitted
Signed-off-by: yminer <yminer@vmware.com>
update UT
update migrate sql for artifact_type
Signed-off-by: yminer <yminer@vmware.com>
remove debug line
Nydus images are compatible with both docker scheme v2 and OCI image spec v1
types of config media type:
- application/vnd.oci.image.config.v1+json
- application/vnd.docker.container.image.v1+json
The patch fixes the media type recognition on the accessory type check.
Signed-off-by: Yan Song <yansong.ys@antgroup.com>
Co-authored-by: MinerYang <yminer@vmware.com>
In certain cases, the OCI client may push the subject artifact and accessory in either order.
Therefore, it is necessary to handle situations where the client pushes the accessory ahead of the subject artifact.
Signed-off-by: wang yan <wangyan@vmware.com>
Recognize nydus image(with subject) as a kind of accessory and built the releationship with subject manifest
Signed-off-by: wang yan <wangyan@vmware.com>
fixes#18865
the response header OCI-Subject to indicate to the client that the registry processed the request's subject.
Signed-off-by: wang yan <wangyan@vmware.com>
Co-authored-by: System Administrator <root@wangyanCQFQY.vmware.com>
As for the distribution spec 1.1, it supports client to push an manifest with subject field. By leverging this fidle, harbor could build up the linkage between the subject artifact and it's accessories.
Signed-off-by: wang yan <wangyan@vmware.com>
MinerYang
stonezdj(Daojun Zhang)
Wang Yan
imeoer