Error handling on harden_manifest step

This template is ONLY used for reporting bugs. New feature request or pipeline enhancement issues should use the other template options for issue submission.

Current Behavior

The harden_manifest stage will run for a long time when there is no version provided for a docker image in the resources section of the hardening_manifest.yaml file (>30 minutes). Then, when the script stops running, the error message shown is incorrect.

Live Example

https://repo1.dsop.io/dsop/kubeflow/common/statsd-0.37.0/-/pipelines/105026

Expected Behavior

The error message shown should reflect that it is a missing tag. The behavior of this script should also time out earlier when faced with an invalid schema item.

Possible Solution

Implement a timeout function for validation if appropriate. Implement better jsonschema error handling.