refactor(artifact): remove oci artifact support#1359
Conversation
|
we also have specific logic for this mediatype in sync: |
8fed5b1 to
0ebd490
Compare
|
https://github.com/regclient/regclient |
aeee3be to
6a79f82
Compare
|
If filtering is requested and applied, the response MUST include a header OCI-Filters-Applied: artifactType denoting that an artifactType filter was applied. If multiple filters are applied, the header MUST contain a comma separated list of applied filters. |
f321ccb to
d133fee
Compare
Codecov Report
@@ Coverage Diff @@
## main #1359 +/- ##
==========================================
+ Coverage 90.70% 90.74% +0.04%
==========================================
Files 99 99
Lines 22390 22032 -358
==========================================
- Hits 20308 19994 -314
+ Misses 1556 1520 -36
+ Partials 526 518 -8
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ba8b4c9 to
779e8a5
Compare
9e7f426 to
1d85ee2
Compare
0d1fb43 to
5efa642
Compare
60a375a to
3bb2247
Compare
|
Results for some tests I did using latest regctl version: link |
3bb2247 to
1755182
Compare
- add header to referrers call to indicated applied artifact type filters Signed-off-by: Laurentiu Niculae <niculae.laurentiu1@gmail.com>
Signed-off-by: Laurentiu Niculae <niculae.laurentiu1@gmail.com>
1755182 to
acaa066
Compare
What type of PR is this?
Which issue does this PR fix:
Closes #1425
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.