anchor.diff:  --------------------------------------------------
   // CONSOLE
   // TESTRESPONSE[skip:There is no way to force the index to move to the next step in a timely manner]
  -<1> The index has moved to using version 2 of the policy
  +<1> The index has moved to using version 3 of the policy
   
   `my_index` will move to the next phase in the latest policy definition, which is the newly added `warm` phase.
   
  
positive.code: // CONSOLE
  // TESTRESPONSE[skip:no way to know if we will get this response immediately]
  
  Updating `my_executing_policy` to have no rollover action and, instead, go directly into a newly introduced `warm` phase.
  
  [source,js]
  ------------------------
  
negative.code: --------------------------------------------------
  // CONSOLE
  // TESTRESPONSE[skip:no way to know if we will get this response immediately]
  <1> the version of the policy used for executing the hot phase
  
  We can also update `my_executing_policy` to have no rollover action and,
  instead, go directly into a newly introduced `warm` phase.
  
  [source,js]
  ------------------------
  PUT _ilm/policy/my_executing_policy
  {
    "policy": {
      "phases": {
        "warm": {
          "min_age": "1d",
          "actions": {
            "forcemerge": {
              "max_num_segments": 1
            }
          }
        },
        "delete": {
          "min_age": "10d",
          "actions": {
            "delete": {}
          }
        }
      }
    }
  }
  ------------------------
  // CONSOLE
  // TEST[continued]
  
  Now, version 3 of this policy has no `hot` phase, but if we run the
  Explain API again, we will see that nothing has changed. The index
  `my_index` is still executing version 1 of the policy.
  
  ////
  [source,js]
  --------------------------------------------------
  GET my_index/_ilm/explain
  --------------------------------------------------
  // CONSOLE
  // TEST[continued]
  ////
  
  [source,js]
  --------------------------------------------------
  {
    "indices": {
      "my_index": {
        "index": "my_index",
        "managed": true,
        "policy": "my_executing_policy",
        "lifecycle_date_millis": 1538475653281,
        "phase": "hot",
        "phase_time_millis": 1538475653317,
        "action": "rollover",
        "action_time_millis": 1538475653317,
        "step": "check-rollover-ready",
        "step_time_millis": 1538475653317,
        "phase_execution": {
          "policy": "my_executing_policy",
          "modified_date_in_millis": 1538475653317,
          "version": 1, <1>
          "phase_definition": {
            "min_age": "0ms",
            "actions": {
              "rollover": {
                "max_docs": 1
              }
            }
          }
        }
      }
    }
  }
  --------------------------------------------------
  // CONSOLE
  // TESTRESPONSE[skip:no way to know if we will get this response immediately]
  <1> the version of the policy used for executing the hot phase
  
  After indexing one document into `my_index` so that rollover succeeds and
  moves onto the next phase, we will notice something new. The index will
  move into the next phase in the updated version 3 of its policy.
  
  ////
  [source,js]
  