Summary: Job status being marked as Success in the event of a failure too, which I've been able to reproduce by specifying wrong credentials and a wrong GUID to run entrypoint.sh, as specified by the user.
This is possibly due to an improper positioning of exitStatus=$? in entrypoint.sh, which is why it was not receiving status 1 in the event of an error. This has been refactored.
41 :
Summary: action.yaml specifies the deployment type input as deploymenttype, but this input has been specified as deploymentType in the examples in README.md. This typo has been fixed.
This PR addresses fixes to the following issues.
40 :
entrypoint.sh, as specified by the user.exitStatus=$?inentrypoint.sh, which is why it was not receiving status1in the event of an error. This has been refactored.41 :
action.yamlspecifies the deployment type input asdeploymenttype, but this input has been specified asdeploymentTypein the examples inREADME.md. This typo has been fixed.Changes made to fix #40 :
Before Changes
After Changes