What is the version of your ORAS CLI
v1.1.0-rc.2
What would you like to be added?
Like #1084, when deleting a manifest, the request 4 and 5 can be avoided if we get a token with delete scope in request 1:
request #0: HEAD manifest tag- 401
request #1: GET token (scope: pull) - 200
request #2: HEAD manifest tag- 200
request #3: GET manifest digest- 200
request #4: DELETE manifest digest 401
request #5: GET token (scope: delete, pull) - 200
request #6: DELETE manifest digest - 202
Same for oras blob delete
Why is this needed for ORAS?
This can further improve the performance of ORAS.
Are you willing to submit PRs to contribute to this feature?
What is the version of your ORAS CLI
v1.1.0-rc.2
What would you like to be added?
Like #1084, when deleting a manifest, the request 4 and 5 can be avoided if we get a token with delete scope in request 1:
request
#0: HEAD manifest tag- 401request
#1: GET token (scope: pull) - 200request
#2: HEAD manifest tag- 200request
#3: GET manifest digest- 200request
#4: DELETE manifest digest 401request
#5: GET token (scope: delete, pull) - 200request
#6: DELETE manifest digest - 202Same for
oras blob deleteWhy is this needed for ORAS?
This can further improve the performance of ORAS.
Are you willing to submit PRs to contribute to this feature?