anchor.diff:        "phase_execution": {
           "policy": "my_executing_policy",
           "modified_date_in_millis": 1538475653317,
  -        "version": 2, <1>
  +        "version": 3, <1>
           "phase_definition": {
             "min_age": "1d",
             "actions": {
  
positive.code: {
    "policy": {
      "phases": {
        "warm": {
          "min_age": "1d",
          "actions": {
            "forcemerge": {
              "max_num_segments": 1
            }
          }
        },
  
negative.code: and an index's `index.lifecycle.name` settings independently. To prevent the situation
  that phase definitions are modified while currently being executed on an index, each index
  will keep the version of the current phase definition it began execution with until it completes.
  This also means that changes to `min_age` will not be propagated. If a new policy is set that
  introduces a later `min_age` for the currently executing phase, that new `min_age` will not
  be picked up by the update.
  
  There are three scenarios for examining the behavior updating policies and
  their effects on policy execution on indices.
  