account for indentation

colleenmcginnis · colleenmcginnis · commit 98db2332af95 · 2025-03-06T21:08:01.000-06:00
diff --git a/deploy-manage/maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md b/deploy-manage/maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md
@@ -84,6 +84,7 @@ Nodes exceeding the low watermark threshold will be slow to restart. Reduce the
 
     GET _cat/nodes
     ```
+    %  TEST[continued]
 
    The `status` column returned by `_cat/health` shows the health of each node in the cluster: `red`, `yellow`, or `green`.
 
@@ -118,6 +119,7 @@ Nodes exceeding the low watermark threshold will be slow to restart. Reduce the
     ```console
     POST _ml/set_upgrade_mode?enabled=false
     ```
+    %  TEST[continued]
 
    If you closed all {{ml}} jobs before stopping the nodes, open the jobs and start the datafeeds from {{kib}} or with the [open jobs](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-open-job) and [start datafeed](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-start-datafeed) APIs.
 
@@ -208,5 +210,6 @@ Nodes exceeding the low watermark threshold will be slow to restart. Reduce the
     ```console
     POST _ml/set_upgrade_mode?enabled=false
     ```
+    %  TEST[continued]
 
    If you closed all {{ml}} jobs before stopping the nodes, open the jobs and start the datafeeds from {{kib}} or with the [open jobs](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-open-job) and [start datafeed](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-start-datafeed) APIs.
diff --git a/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md b/deploy-manage/monitor/stack-monitoring/es-legacy-collection-methods.md
@@ -49,6 +49,7 @@ To learn about monitoring in general, see [Monitor a cluster](../../monitor.md).
         ```console
         GET _cluster/settings
         ```
+        %  TEST[warning:[xpack.monitoring.collection.enabled] setting was deprecated in Elasticsearch and will be removed in a future release.]
 
         ```console
         PUT _cluster/settings
diff --git a/deploy-manage/security/different-ca.md b/deploy-manage/security/different-ca.md
@@ -145,6 +145,7 @@ If your organization has its own CA, you’ll need to [generate Certificate Sign
     ```console
     GET /_ssl/certificates
     ```
+    %  TEST[skip:creates a lot of noise]
 
 7. If you’re only updating certificates for the transport layer (and not the HTTP layer), then complete [step 2](#start-rolling-restart-newca) through [step 6](#verify-keystore-newca) one node at a time until you’ve updated all keystores in your cluster. You can then complete the remaining steps for a [rolling restart](../maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md#restart-cluster-rolling).
 
@@ -275,6 +276,7 @@ This process is different for each client, so refer to your client’s documenta
     ```console
     GET /_ssl/certificates
     ```
+    %  TEST[skip:creates a lot of noise]
 
 11. One node at a time, complete [step 5](#start-rolling-restart-http-newca) through [step 10](#verify-keystore-http-newca) until you’ve updated all keystores in your cluster.
 12. Complete the remaining steps for a [rolling restart](../maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md#restart-cluster-rolling), beginning with the step to **Reenable shard allocation**.
diff --git a/deploy-manage/security/same-ca.md b/deploy-manage/security/same-ca.md
@@ -98,6 +98,7 @@ The following examples use PKCS#12 files, but the same steps apply to JKS keysto
     ```console
     GET /_ssl/certificates
     ```
+    %  TEST[skip:creates a lot of noise]
 
 9. If you’re only updating certificates for the transport layer (and not the HTTP layer), then complete [step 4](#start-rolling-restart) through [step 8](#verify-keystore) one node at a time until you’ve updated all keystores in your cluster. You can then complete the remaining steps for a [rolling restart](../maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md#restart-cluster-rolling).
 
@@ -205,6 +206,7 @@ If your organization has its own CA, you’ll need to [generate Certificate Sign
     ```console
     GET /_ssl/certificates
     ```
+    %  TEST[skip:creates a lot of noise]
 
 11. One node at a time, complete [step 5](#start-rolling-restart-http) through [step 10](#verify-keystore-http) until you’ve updated all keystores in your cluster.
 12. Complete the remaining steps for a [rolling restart](../maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures.md#restart-cluster-rolling), beginning with the step to **Reenable shard allocation**.
diff --git a/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md b/deploy-manage/tools/snapshot-and-restore/restore-snapshot.md
@@ -465,6 +465,7 @@ DELETE my-index
 # Delete a data stream
 DELETE _data_stream/logs-my_app-default
 ```
+%  TEST[setup:setup-snapshots]
 
 
 ## Restore to a different cluster [restore-different-cluster]
diff --git a/deploy-manage/tools/snapshot-and-restore/shared-file-system-repository.md b/deploy-manage/tools/snapshot-and-restore/shared-file-system-repository.md
@@ -139,6 +139,8 @@ PUT _snapshot/my_fs_backup
   }
 }
 ```
+%  TEST[skip:no access to path]
+::::::
 ::::::
 
 :::::::
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md b/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-sm.md
@@ -58,6 +58,7 @@ POST /_security/user/user1/_password
   "password" : "new-test-password"
 }
 ```
+% TEST[continued]
 
 For more information and examples, see [Users](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security).
 
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md b/deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md
@@ -479,6 +479,7 @@ Audiences:  aud8
 Algorithms: HS256
 HMAC UTF-8: hmac-oidc-key-string-for-hs256-algorithm
 ```
+%  NOTCONSOLE
 
 
 ### JWT realm settings [hmac-oidc-example-jwt-realm]
diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md b/deploy-manage/users-roles/cluster-or-deployment-auth/saml.md
@@ -811,6 +811,7 @@ POST /_security/saml/authenticate
   "ids" : []
 }
 ```
+%  TEST[skip:handled in IT]
 
 
 ### Handling the logout flow [saml-no-kibana-slo]
diff --git a/explore-analyze/query-filter/languages/sql-getting-started.md b/explore-analyze/query-filter/languages/sql-getting-started.md
@@ -57,4 +57,6 @@ sql> SELECT * FROM library WHERE release_date < '2000-01-01';
 Dan Simmons    |Hyperion       |482            |1989-05-26T00:00:00.000Z
 Frank Herbert  |Dune           |604            |1965-06-01T00:00:00.000Z
 ```
+%  TESTRESPONSE[s/|/\|/ s/+/\+/]
+%  TESTRESPONSE[non_json]
 
diff --git a/explore-analyze/scripting/scripting-field-extraction.md b/explore-analyze/scripting/scripting-field-extraction.md
@@ -240,6 +240,7 @@ Looking at the data again, there’s a timestamp, some other data that you’re
 ```txt
 [2021-04-27T16:16:34.699+0000][82460][gc,heap,exit]   class space    used 266K, capacity 384K, committed 384K, reserved 1048576K
 ```
+%  NOTCONSOLE
 
 You can assign variables to each part of the data in the `gc` field, and then return only the parts that you want. Anything in curly braces `{}` is considered a variable. For example, the variables `[%{@timestamp}][%{{code}}][%{{desc}}]` will match the first three chunks of data, all of which are in square brackets `[]`.
 
diff --git a/explore-analyze/transforms/ecommerce-transforms.md b/explore-analyze/transforms/ecommerce-transforms.md
@@ -307,6 +307,7 @@ mapped_pages:
    ```console
    POST _transform/ecommerce-customer-transform/_start
    ```
+   %  TEST[skip:setup kibana sample data]
 
    ::::
 
diff --git a/explore-analyze/transforms/transform-painless-examples.md b/explore-analyze/transforms/transform-painless-examples.md
@@ -173,6 +173,7 @@ You can also use the power of [stored scripts](https://www.elastic.co/docs/api/d
                 "id":"last-value-reduce"
              }
     ```
+    %  NOTCONSOLE
 
     1. The parameter `field_with_last_value` can be set any field that you want the latest value for.
 
diff --git a/manage-data/data-store/data-streams/modify-data-stream.md b/manage-data/data-store/data-streams/modify-data-stream.md
@@ -340,6 +340,7 @@ Follow these steps:
     ```console
     PUT /_data_stream/new-data-stream
     ```
+    %  TEST[s/new-data-stream/new-data-stream-two/]
 
 4. If you do not want to mix new and old data in your new data stream, pause the indexing of new documents. While mixing old and new data is safe, it could interfere with data retention. See [Mixing new and old data in a data stream](../data-streams/modify-data-stream.md#data-stream-mix-new-old-data).
 5. If you use {{ilm-init}} to [automate rollover](../../lifecycle/index-lifecycle-management/tutorial-automate-rollover.md), reduce the {{ilm-init}} poll interval. This ensures the current write index doesn’t grow too large while waiting for the rollover check. By default, {{ilm-init}} checks rollover conditions every 10 minutes.
diff --git a/manage-data/data-store/templates/ignore-missing-component-templates.md b/manage-data/data-store/templates/ignore-missing-component-templates.md
@@ -102,4 +102,6 @@ This will not have an immediate effect on the data stream. The mapping `host.ip`
 ```console
 POST logs-foo-bar/_rollover
 ```
+%  TEST[continued]
+%  TEST[teardown:data_stream_cleanup]
 
diff --git a/manage-data/ingest/transform-enrich/example-parse-logs.md b/manage-data/ingest/transform-enrich/example-parse-logs.md
@@ -141,6 +141,7 @@ These logs contain a timestamp, IP address, and user agent. You want to give the
     ```console
     GET my-data-stream/_search?filter_path=hits.hits._source
     ```
+    %  TEST[continued]
 
     The API returns:
 
diff --git a/manage-data/ingest/transform-enrich/ingest-pipelines.md b/manage-data/ingest/transform-enrich/ingest-pipelines.md
@@ -321,6 +321,7 @@ $$$pipeline-custom-logs-index-template$$$
     ```console
     POST logs-my_app-default/_rollover/
     ```
+    %  TEST[continued]
 
 
 $$$pipeline-custom-logs-configuration$$$
diff --git a/manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md b/manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
@@ -138,6 +138,7 @@ Considering our example, if we retrieve the lifecycle of `my-data-stream`:
 ```console
 GET _data_stream/my-data-stream/_lifecycle
 ```
+%  TEST[continued]
 
 We see that it will remain the same with what the user configured:
 
diff --git a/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md b/manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md
@@ -213,12 +213,14 @@ To switch an index’s lifecycle policy, follow these steps:
     ```console
     GET logs-my_app-default
     ```
+    %  TEST[continued]
 
     You can then change the index as needed. For example, you can re-open any closed indices using the [open index API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-open).
 
     ```console
     POST logs-my_app-default/_open
     ```
+    %  TEST[continued]
 
 3. Assign a new policy using the [update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-put-settings). Target a data stream or alias to assign a policy to all its indices.
 
diff --git a/solutions/search/retrievers-examples.md b/solutions/search/retrievers-examples.md
@@ -1362,6 +1362,7 @@ GET retrievers_example/_search
     "_source": false
 }
 ```
+%  TEST[skip: no_access_to_ml]
 
 
 ## Example: RRF with semantic reranker [retrievers-examples-rrf-ranking-on-text-similarity-reranker-results]
@@ -1410,6 +1411,7 @@ GET /retrievers_example/_search
     "_source": false
 }
 ```
+%  TEST[skip: no_access_to_ml]
 
 
 ## Example: Chaining multiple semantic rerankers [retrievers-examples-chaining-text-similarity-reranker-retrievers]
diff --git a/solutions/search/search-applications/search-application-api.md b/solutions/search/search-applications/search-application-api.md
@@ -545,6 +545,7 @@ Finally, a parameterless search using this template would fall back to a default
 ```console
 POST _application/search_application/my_search_application/_search
 ```
+%  TEST[continued]
 
 
 ### ELSER search [search-application-api-elser-template]
diff --git a/solutions/search/vector/knn.md b/solutions/search/vector/knn.md
@@ -226,6 +226,9 @@ POST byte-image-index/_search
   "fields": [ "title" ]
 }
 ```
+%  TEST[continued]
+%  TEST[s/"k": 10/"k": 3/]
+%  TEST[s/"num_candidates": 100/"num_candidates": 3/]
 
 
 ### Byte quantized kNN search [knn-search-quantized-example]
@@ -322,6 +325,9 @@ POST quantized-image-index/_search
   }
 }
 ```
+%  TEST[continued]
+%  TEST[s/"k": 15/"k": 3/]
+%  TEST[s/"num_candidates": 100/"num_candidates": 3/]
 
 
 ### Filtered kNN search [knn-search-filter-example]
@@ -747,6 +753,7 @@ Now we have filtered based on the top level `"creation_time"` and only one docum
     }
 }
 ```
+%  TESTRESPONSE[s/"took": 4/"took" : "$body.took"/]
 
 
 ### Nested kNN Search with Inner hits [nested-knn-search-inner-hits]
diff --git a/troubleshoot/elasticsearch/add-tier.md b/troubleshoot/elasticsearch/add-tier.md
@@ -40,6 +40,7 @@ In order to get the shards assigned we need enable a new tier in the deployment.
     ```console
     GET /my-index-000001/_settings/index.routing.allocation.include._tier_preference?flat_settings
     ```
+    %  TEST[continued]
 
     The response will look like this:
 
diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md
@@ -38,6 +38,7 @@ In order to check the status of failing {{slm}} policies we need to go to Kibana
     ```console
     GET _slm/policy/<affected-policy-name>
     ```
+    %  TEST[skip:These policies do not exist]
 
     The response will look like this:
 
diff --git a/troubleshoot/elasticsearch/restore-from-snapshot.md b/troubleshoot/elasticsearch/restore-from-snapshot.md
@@ -38,6 +38,7 @@ In order to restore the indices and data streams that are missing data:
     ```console
     GET _cat/indices?v&health=red&h=index,status,health
     ```
+    %  TEST[skip:illustration purposes only]
 
     The response will look like this:
 
@@ -54,6 +55,7 @@ In order to restore the indices and data streams that are missing data:
     ```console
     GET _snapshot/my_repository/*?verbose=false
     ```
+    %  TEST[skip:illustration purposes only]
 
     The response will look like this:
 
@@ -149,6 +151,7 @@ In order to restore the indices and data streams that are missing data:
     ```console
     POST my-data-stream/_rollover
     ```
+    %  TEST[skip:illustration purposes only]
 
 8. Now that the data stream preparation is done, we will close the target indices by using the [close indices API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-close).
 
@@ -161,6 +164,7 @@ In order to restore the indices and data streams that are missing data:
     ```console
     GET _cat/indices?v&health=red&h=index,status,health
     ```
+    %  TEST[skip:illustration purposes only]
 
     The response will look like this:
 
@@ -242,6 +246,7 @@ In order to restore the indices that are missing shards:
     ```console
     GET _snapshot/my_repository/*?verbose=false
     ```
+    %  TEST[skip:illustration purposes only]
 
     The response will look like this:
 
@@ -337,6 +342,7 @@ In order to restore the indices that are missing shards:
     ```console
     POST my-data-stream/_rollover
     ```
+    %  TEST[skip:illustration purposes only]
 
 5. Now that the data stream preparation is done, we will close the target indices by using the [close indices API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-close).
 
diff --git a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
@@ -41,6 +41,7 @@ If you’re confident your changes won’t destabilize the cluster, you can temp
     ```console
     GET _health_report/shards_capacity
     ```
+    %  TESTRESPONSE[skip:the result is for illustrating purposes only]
 
     The response will look like this:
 
diff --git a/troubleshoot/elasticsearch/watcher-troubleshooting.md b/troubleshoot/elasticsearch/watcher-troubleshooting.md
@@ -26,6 +26,7 @@ If the index mappings are missing, follow these steps to restore the correct map
     ```console
     DELETE .watches
     ```
+    %  TEST[skip:index deletion and deprecation warning]
 
 5. Disable direct access to the `.watches` index:
 

Original file line number	Diff line number	Diff line change
`@@ -139,6 +139,8 @@ PUT _snapshot/my_fs_backup`
`139`	`139`	`}`
`140`	`140`	`}`
`141`	`141`	```
	`142`	`+% TEST[skip:no access to path]`
	`143`	`+::::::`
`142`	`144`	`::::::`
`143`	`145`
`144`	`146`	`:::::::`
Original file line number	Diff line number	Diff line change
`@@ -58,6 +58,7 @@ POST /_security/user/user1/_password`
`58`	`58`	`"password" : "new-test-password"`
`59`	`59`	`}`
`60`	`60`	```
	`61`	`+% TEST[continued]`
`61`	`62`
`62`	`63`	`For more information and examples, see [Users](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security).`
`63`	`64`
Original file line number	Diff line number	Diff line change
`@@ -811,6 +811,7 @@ POST /_security/saml/authenticate`
`811`	`811`	`"ids" : []`
`812`	`812`	`}`
`813`	`813`	```
	`814`	`+% TEST[skip:handled in IT]`
`814`	`815`
`815`	`816`
`816`	`817`	`### Handling the logout flow [saml-no-kibana-slo]`