In our patching process, we utilise the "before and after" patching command. We do this to gracefully stop services on a server, let the system patch, and then start them once patching is complete.
On a recent patching cycle, the "before" patching command executed as normal, however there was a issue with the "patching" part of the process, which got a 404 one of the linux patches.
this then caused anything further down the process to be aborted, including the start command
Is there any possibility to make the start process run even if the "patching" part of the process fails, and remove the dependancy on every step completing successfully? e.g. if the pre-patch command runs, the post-patch command must always run.
