Skip to content
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

Output Digest When Pushing OCI Artifacts #126

Closed
duffney opened this issue Nov 5, 2024 · 2 comments · Fixed by #138
Closed

Output Digest When Pushing OCI Artifacts #126

duffney opened this issue Nov 5, 2024 · 2 comments · Fixed by #138

Comments

@duffney
Copy link

duffney commented Nov 5, 2024

When pushing an OCI artifact, users often need the digest immediately to proceed with signing workflows or for downstream automation. Both docker push and oras push output the digest as part of their operations, which streamlines integration with signing and verification tools. Without this feature in wkg, users must perform additional steps (like inspecting the registry) to retrieve the digest, which adds unnecessary overhead and slows down secure supply chain workflows.

Proposed Solution: Update wkg to display the artifact digest upon a successful push. This behavior would align wkg with other popular tools (e.g., docker and oras) and enhance usability for security-focused workflows. By outputting the digest, wkg will better support secure supply chain practices, making it easier for users to incorporate artifact verification directly into their CI/CD pipelines.

Something like this would be awesome!

wkg oci push myartifact:v1
Pushed artifact myartifact:v1
Digest: sha256:<digest_here>
@calvinrp
Copy link
Collaborator

calvinrp commented Nov 6, 2024

Happy to accept the PR for this! Small change.

@duffney
Copy link
Author

duffney commented Nov 14, 2024

Awesome! I'll start working on a PR. Thank you for the reply. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants