You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CodeDeploy is missing a mechanism for doing cleanup after a deployment error. This could be implemented as another lifecycle event that is triggered only when a deployment fails for some reason. This reason could be e.g. a non-zero exit status of a hook script, a timeout or a user-triggered cancellation of the deployment.
CodeDeploy is missing a mechanism for doing cleanup after a deployment error. This could be implemented as another lifecycle event that is triggered only when a deployment fails for some reason. This reason could be e.g. a non-zero exit status of a hook script, a timeout or a user-triggered cancellation of the deployment.
The idea of this originates from a more specific issue regarding ASG lifecycle scripts. In that case, an auto-scaling group is left in an unclean state after an error during a deployment.
One remotely similar mechanism for error handling is the
rescue
block in Ansible:http://docs.ansible.com/ansible/playbooks_blocks.html
The text was updated successfully, but these errors were encountered: