-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Assets: Always use source file for hash #4100
Conversation
When we're computing the expected hash, we should always use the original source file. In this way we pick up problems where the source file was not mirrored correctly.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Follow on with nits to #3254 |
Yah as we have talked about kops may not have access to the source file hash. kops is run using asessts phase in a non air gapped environment, and then is run using other phases where it may not have access to gcr.io and googlestorage.com. So I understand why you want this, you have any other solutions? |
/hold |
See /hold |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
When we're computing the expected hash, we should always use the
original source file. In this way we pick up problems where the source
file was not mirrored correctly.