0.15.3
- step function error handling for lambda resource not found error
- if a lambda is redeployed while a job is running, sometimes step function tries to access the lambda during the very short period of time after the lambda function is deleted and before an updated function is uploaded. In this rare case, step functions would throw a lambda resource not found error. From 0.15.3, this error is ignored and retried a few more times. In short, the currently running jobs are not sensitive to redeployment any more.
- Redeploy the whole unicorn for this to take effect.
tibanna deploy_unicorn -b buckets [-g groupname] [-s suffix]