Optimize the push image processing logic when the quota is full

[lengrongfu]

What can we help you?

The current image push logic is to post first and then put the image push. When the project quota is full, it will not return whether the quota has been exceeded until the put push is completed.
Hope to optimize to fail-fast logic and perform quota verification when executing post init interface requests.

[lengrongfu]

• The following is the effect of the push after my modification

[root@localhost ~]# docker push test.harbor.com/library/ubuntu
The push refers to repository [test.harbor.com/library/ubuntu]
629d9dbab5ed: Preparing
denied: subtracting 0 B of storage resource, which when updated to current usage of 187.5 MiB will exceed the configured upper limit of 10.0 MiB.

• The following is the effect of the push before I modified

[root@localhost ~]# docker push test.harbor.com/library/ubuntu
The push refers to repository [test.harbor.com/library/ubuntu]
629d9dbab5ed: Pushing  80.35MB
denied: adding 29.0 MiB of storage resource, which when updated to current usage of 152.4 MiB will exceed the configured upper limit of 10.0 MiB.

It fails on calling the first interface, so there is no data transfer.

[lengrongfu]

Hi, Is there anything to discuss this issue and PR?
@Vad1mo

[lengrongfu]

Hi, feel free to post any thoughts on this issuer, please let me know what the community thinks.
@wy65701436

[lengrongfu]

@zyyw @wy65701436 Do you have any questions about this issue?