hashing support

[pschrammel]

I need some help here to have hashing configurable

[guilhermef]

Hi @pschrammel, what's the use case for hashing in the storage?

[pschrammel]

It is a feature of TC_AWS that we were using for several reasons:

• we use full urls (with https:// ....) to load the original image and that was leading to very strange s3 keys
• we don't want to have our url structure visible in s3

I switched from sha1 (original in TC_AWS) to sha256 as sha1 is regarded unsafe by our security scanners though in this case it wouldn't matter

[pschrammel]

@guilhermef , I changed the concept, getting my very specific hashing is hard to get upstream. The idea now is that you can define a lambda expression that does your personal normalization magic. I hope this approach is more generic and easier to accept.

[coveralls]

Pull Request Test Coverage Report for Build 9775890186

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 20 of 20 (100.0%) changed or added relevant lines in 4 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.07%) to 91.618%

---

Totals
Change from base Build 9687721972:	0.07%
Covered Lines:	317
Relevant Lines:	346

---

💛 - Coveralls