I would like the helm deploy task to support checksum sha1 header generation for JFrog artifactory and that should solve the warning message on default JFrog Artifactory repository policy:
Client did not publish a checksum value.
If you trust the uploaded artifact you can accept the actual checksum by clicking the 'Fix Checksum' button.
It's quite easy/common for files to become corrupted during file transfer or even after deployment;
by using this Checksum-Policy option (making sure that the client's provided checksum matches
the one calculated by Artifactory), the user is ensuring the file's data-integrity has not been compromised.
JFrog artifactory header name for checksum is: -H "X-Checksum-Sha1:<hex_sha1_diggest>"
I would like the helm deploy task to support checksum sha1 header generation for JFrog artifactory and that should solve the warning message on default JFrog Artifactory repository policy:
Why do we need it? Note from JFrog (https://jfrog.com/knowledge-base/what-are-client-checksum-server-checksum-and-checksum-policy-in-local-repositories/ )
JFrog artifactory header name for checksum is:
-H "X-Checksum-Sha1:<hex_sha1_diggest>"