anchor.diff:  -----------------------
   // TEST[continued]
   
  +<1> Apply the template to a new index if its name starts with `datastream-`. 
  +<2> The name of the lifecycle policy to apply to each new index.
  +<3> The name of the alias used to reference these indices. 
  +Required for policies that use the rollover action.
  +
   //////////////////////////
   
   [source,console]
  
positive.code: --------------------------------------------------
  // TESTRESPONSE[skip:no way to know if we will get this response immediately]
  
  <1> this index is managed by ILM
  <2> the policy in question, in this case, "datastream_policy"
  <3> the current age of the index
  <4> what phase the index is currently in
  <5> what action the index is currently on
  <6> what step the index is currently on
  <7> the definition of the phase
      (in this case, the "hot" phase) that the index is currently on
  <8> the version of the policy being used to execute the current phase
  
  You can read about the full details of this response in the
  <<ilm-explain-lifecycle, explain API docs>>. For now, let's focus on how
  the response details which phase, action, and step we're in. We are in the
  "hot" phase, and "rollover" action. Rollover will continue to be called
  by {ilm-init} until its conditions are met and it rolls over the index.
  Afterwards, the original index will stay in the hot phase until 90 more
  days pass and it is deleted in the delete phase.
  As time goes on, new indices will be created and deleted.
  With `datastream-000002` being created when the index mets the rollover
  conditions and `datastream-000003` created after that. We will be able
  to search across all of our managed indices using the "datastream" alias,
  and we will be able to write to our to-be-rolled-over write indices using
  that same alias.
  
  
  
  That's it! We have our first use-case managed by {ilm-init}.
  
  To learn more about all our APIs,
  check out <<index-lifecycle-management-api,ILM APIs>>.
  
negative.code: 
  //////////////////////////
  
  [float]
  [[ilm-gs-bootstrap]]
  === Bootstrap the initial time-series index
  
  To get things started, you need to bootstrap an initial index and 
  designate it as the write index for the rollover alias specified in your index template. 
  The name of this index must match the template's index pattern and end with a number. 
  On rollover, this value is incremented to generate a name for the new index. 
  
  For example, the following request creates an index called `datastream-000001` 
  and makes it the write index for the `datastream` alias.
  
  [source,console]
  -----------------------
  