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

[FR] Push dist/gcp/*.sha256 files to public repo when building releases for GCP #11

Open
roscoejp opened this issue Feb 29, 2024 · 1 comment
Assignees

Comments

@roscoejp
Copy link

It looks like the ./production/packaging/build_and_test_all_in_docker script creates artifacts in the dist/gcp directory that includes *.sha256 files for the binary hashes of a particular build.

If these hash files were uploaded to the repo when a public release is created, they could be used for direct comparison against local/operator built images. This would make public validation of Google's provided hashes a bit easier compared to the current method of scraping the release notes.

@dankocoj-google
Copy link
Collaborator

dankocoj-google commented Apr 19, 2024

Good idea Roscoe, I'll work on this. We'll also probably publish artifacts in a format like
<service_name>.<aws|gcp>.hash

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

No branches or pull requests

2 participants