feat: use Referrers API per OCI v1.1 spec #602
feat: use Referrers API per OCI v1.1 spec #602patrickzheng200 merged 1 commit intonotaryproject:mainfrom
Conversation
Signed-off-by: Patrick Zheng <patrickzheng@microsoft.com>
patrickzheng200
requested review from
JeyJeyGao,
NiazFK,
SteveLasker,
gokarnm,
justincormack,
priteshbandi,
rgnote and
shizhMSFT
as code owners
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #602 +/- ##
==========================================
+ Coverage 34.36% 34.45% +0.09%
==========================================
Files 32 32
Lines 1848 1843 -5
==========================================
Hits 635 635
+ Misses 1192 1187 -5
Partials 21 21
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
qweeah
left a comment
qweeah
left a comment
There was a problem hiding this comment.
LGTM but IANAM. Just a question: why notation need to detect the support status of referrer API? Shouldn't it be automatically taken care of from oras-go side?
Correct. The fallback logic is indeed in oras-go. |
when storing signature using oci image manifest, the Referrers API will be used. If Referrers API is not supported, automatically fallback to use Referrers Tag Schema. Signed-off-by: Josh Duffney <jduffney@microsoft.com>
when storing signature using oci image manifest, the Referrers API will be used. If Referrers API is not supported, automatically fallback to use Referrers Tag Schema.
when storing signature using oci image manifest, the Referrers API will be used. If Referrers API is not supported, automatically fallback to use Referrers Tag Schema.
7 participants
This PR: when storing signature using oci image manifest, the Referrers API will be used. If Referrers API is not supported, automatically fallback to use Referrers Tag Schema.
Resolves #575.