-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Image size and mod timestamp #6
Comments
Been a bit since I worked on the manifests, so can you explain how this is used? No issues with it, but always want to understand the use case.
Hmm, again, what is the use case? |
My use case is that I'm writing a backup script to stuff my older images into S3 storage. I want to pull accurate timestamps in order to implement algorithms like "keep the past 7 days". I also want to check sizes so that I can verify that a backup currently exists in S3, and has a size that's close to the size of the tag in my local repo. On a side note, I already implemented this in my wrapper class, it'd just be nice to have in the gem:
|
Finally coming back to this after a while. On the first part, no need to ask for the sizes via HEAD, they are in the manifest. Putting it in right now. |
Can you add in a method to sum up the sizes from each of the blobs from an image tag? (Using the API HEAD call to
/v2/#{image}/blobs/#{blobSum}
)Also, it would be nice to have a convenience method to run through the
v1Compatibility
elements, find the most recent, and return a Time object that represents the tag's upload time.Thank you!
The text was updated successfully, but these errors were encountered: