Browse Source

[TEST] ILM skip checking _ilm/explain response (#35830)

relates #35562

Closes #35824.
Tal Levy 6 years ago
parent
commit
a0f8a22d53
1 changed files with 1 additions and 5 deletions
  1. 1 5
      docs/reference/ilm/update-lifecycle-policy.asciidoc

+ 1 - 5
docs/reference/ilm/update-lifecycle-policy.asciidoc

@@ -301,11 +301,7 @@ GET my_index/_ilm/explain
 }
 --------------------------------------------------
 // CONSOLE
-// TESTRESPONSE[s/"lifecycle_date_millis": 1538475653281/"lifecycle_date_millis": $body.indices.my_index.lifecycle_date_millis/]
-// TESTRESPONSE[s/"phase_time_millis": 1538475653317/"phase_time_millis": $body.indices.my_index.phase_time_millis/]
-// TESTRESPONSE[s/"action_time_millis": 1538475653317/"action_time_millis": $body.indices.my_index.action_time_millis/]
-// TESTRESPONSE[s/"step_time_millis": 1538475653317/"step_time_millis": $body.indices.my_index.step_time_millis/]
-// TESTRESPONSE[s/"modified_date_in_millis": 1538475653317/"modified_date_in_millis": $body.indices.my_index.phase_execution.modified_date_in_millis/]
+// TESTRESPONSE[skip:no way to know if we will get this response immediately]
 
 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 2 of its policy.