#14 DC3DD_EXIT_HASH_MISMATCH

[Beren Scott]

So far, I have added in curl commands into DC3DD_EXIT_COMPLETED and DC3DD_EXIT_FAILED.

This gives a level of automation into the mix. But, what I am thinking is that DC3DD_EXIT_HASH_MISMATCH might need to be an option. And this might be based on my inability to adequately resolve the question of whether the program considers the exit code to be DC3DD_EXIT_COMPLETED or DC3DD_EXIT_FAILED if the hash mismatches. Do we consider a failed hash check to be completed or failed?

So, what I was considering is perhaps a better option would be to make it a little bit more clearer. Including it as an exit code. Further to that, an option could be set in how to interpret a failed hash check. From basic levels of searching a failed hash check seems to only alter the way that reporting is handled, which from the outside means checking logs. I could absolutely be wrong here. I probably shouldn't be automating within the code, but the choice to do so is merely code obfuscation. Then again, if this is a possible feature of adding in API calls, then I'm open to submitting my very poor code.