Add support for --digestfile for skopeo sync#2402
Conversation
|
We were not able to find or create Copr project Unless the HTTP status code above is >= 500, please check your configuration for:
|
--digestfile for skopeo sync
mtrmac
left a comment
There was a problem hiding this comment.
Thanks!
Did you try running the PR? AFAICS this would keep overwriting the same file with digests, and in effect only record the last digest of them. I don’t see how that’s useful.
|
Also, https://github.com/containers/skopeo/blob/main/CONTRIBUTING.md#sign-your-prs ; we can’t really even look at PRs with unclear copyright status. |
0172d87 to
7142b58
Compare
hey @mtrmac |
Done. |
|
LGTM |
1b861a3 to
4932405
Compare
@mtrmac can you please give it a poke. |
43746a1 to
279ee95
Compare
Ran the changes on local and validated the output for manifest file. |
mtrmac
left a comment
There was a problem hiding this comment.
Thanks!
One last thing, and please squash the commits into one.
* Digest file output would have docker reference of source and sha of of the mainfest sync'd with the target. This file would not be created if dry-run flag is enabled * improved the sync document to include the correct output for manifest file. * added new line for the manifest file once all images are sync'd * Ensuring we log on manifest digest if the copy operation was successful. * Check for errors if any once sync process is complete. * Ensure to capture the failure when closing the manifest file. * Ensure we are not writing manifest sha for failed copy of imagesand aborting the process in case write to file fails Signed-off-by: Ankit Agarwal <aagarwal@cloudsmith.io>
88ff098 to
10a9e24
Compare
Added
--digestfilefor skopeosyncoptiondry-runflag is set.