Document mid lifecycle hooks

Author: 0xmichalis

dev_guide/deployments.adoc

@@ -48,31 +48,31 @@ following is an example of a `*deploymentConfig*` resource:
 ----
 kind: "DeploymentConfig"
 apiVersion: "v1"
-metadata: 
+metadata:
   name: "frontend"
-spec: 
+spec:
   template: <1>
-    metadata: 
-      labels: 
+    metadata:
+      labels:
         name: "frontend"
-    spec: 
-      containers: 
+    spec:
+      containers:
         - name: "helloworld"
           image: "openshift/origin-ruby-sample"
-          ports: 
+          ports:
             - containerPort: 8080
               protocol: "TCP"
   replicas: 5 <2>
-  selector: 
+  selector:
     name: "frontend"
-  triggers: 
+  triggers:
     - type: "ConfigChange" <3>
     - type: "ImageChange" <4>
-      imageChangeParams: 
+      imageChangeParams:
         automatic: true
-        containerNames: 
+        containerNames:
           - "helloworld"
-        from: 
+        from:
           kind: "ImageStreamTag"
           name: "origin-ruby-sample:latest"
   strategy: <5>
@@ -239,7 +239,7 @@ The following is an example of a ConfigChange trigger:
 
 [source,yaml]
 ----
-triggers: 
+triggers:
   - type: "ConfigChange"
 ----
 ====
@@ -256,14 +256,14 @@ The following is an example of an ImageChange trigger:
 
 [source,json]
 ----
-triggers: 
+triggers:
   - type: "ImageChange"
-    imageChangeParams: 
+    imageChangeParams:
       automatic: true <1>
-      from: 
+      from:
         kind: "ImageStreamTag"
         name: "origin-ruby-sample:latest"
-      containerNames: 
+      containerNames:
         - "helloworld"
 ----
 <1> If the `*automatic*` option is set to `false`, the trigger is disabled.
@@ -383,17 +383,19 @@ strategy:
   type: Recreate
   recreateParams: <1>
     pre: {} <2>
+    mid: {}
     post: {}
 ----
 
 <1> `*recreateParams*` are optional.
-<2> `*pre*` and `*post*` are both xref:lifecycle-hooks[lifecycle hooks].
+<2> `*pre*`, `*mid*`, and `*post*` are both xref:lifecycle-hooks[lifecycle hooks].
 ====
 
 The Recreate strategy will:
 
 . Execute any "pre" lifecycle hook.
 . Scale down the previous deployment to zero.
+. Execute any "mid" lifecycle hook.
 . Scale up the new deployment.
 . Execute any "post" lifecycle hook.
 
@@ -402,8 +404,6 @@ than one, the  first replica of the deployment will be validated for readiness
 before fully scaling up the deployment. If the validation of the first replica
 fails, the deployment will be considered a failure.
 
-IMPORTANT: When executing the "post" lifecycle hook, all failures will be
-ignored regardless of the failure policy specified on the hook.
 
 [[custom-strategy]]