Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
allow using the promoter for diffing GCR contents #134
The new flags are
This is because tagless promotions, by definition, cannot overlap with each other (as the only "pointer" to them are digests which act as checksums of the content). So, they should always be included. Also add unit tests.
This flag can condense all of the manifest information from a -manifest-dir, and output a complete inventory of all images we would like to promote (filtered by the given destination registry name). This is useful if, for example, we would like to know the complete catalogue of all images that we would like to "exist" at a destination registry, using the promoter manifests alone as the source of truth. In a sense, this flag can be thought of as a sort of "manifest" normalizer that can create a new manifest out of a bunch of smaller manifest files (at least the `images:` portion of it). This comes in handy in case we want to cross-reference the output of -snapshot against a known good set of promoter manifests that are solely responsible for adding new images to the snapshotted repo, for purposes of auditing.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: listx
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing
This flag removes all digests that are referenced by a DockerManifestList. This results in a much more compact output, because ManifestLists frequently refer to tagless child digests. The new functions are patterned after the existing ReadRegistries() function, so there are many parallels.