New feature, improvement proposal

Right now, we have one single configuration key that controls both, generation of theirs on deploy, and retrieval on consumption. Make it possible to:

• have one key as today
• but, if user wants, split checksums generated on deploy (ie. user may want sha512 deployed) and checksums looked for on consumption.