add es code comments for testing

Author: colleenmcginnis

deploy-manage/deploy/self-managed/install-elasticsearch-from-archive-on-linux-macos.md

@@ -69,6 +69,7 @@ curl https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-9.0.0-be
 tar -xzf elasticsearch-9.0.0-beta1-darwin-x86_64.tar.gz
 cd elasticsearch-9.0.0-beta1/ <2>
 ```
+%  NOTCONSOLE
 
 1. Compares the SHA of the downloaded `.tar.gz` archive and the published checksum, which should output `elasticsearch-{{version}}-darwin-x86_64.tar.gz: OK`.
 2. This directory is known as `$ES_HOME`.
@@ -164,6 +165,7 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert $ES_HOME/config/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
+%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.

deploy-manage/deploy/self-managed/install-elasticsearch-with-debian-package.md

@@ -211,6 +211,7 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert /etc/elasticsearch/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
+%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.

deploy-manage/deploy/self-managed/install-elasticsearch-with-rpm.md

@@ -215,6 +215,7 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert /etc/elasticsearch/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
+%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.

deploy-manage/deploy/self-managed/install-elasticsearch-with-zip-on-windows.md

@@ -142,6 +142,7 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert %ES_HOME%\config\certs\http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
+%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.

deploy-manage/deploy/self-managed/local-development-installation-quickstart.md

@@ -35,6 +35,7 @@ To set up {{es}} and {{kib}} locally, run the `start-local` script:
 ```sh
 curl -fsSL https://elastic.co/start-local | sh
 ```
+%  NOTCONSOLE
 
 This script creates an `elastic-start-local` folder containing configuration files and starts both {{es}} and {{kib}} using Docker.
 

deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/delaying-allocation-when-node-leaves.md

@@ -37,6 +37,7 @@ PUT _all/_settings
   }
 }
 ```
+%  TEST[s/^/PUT test\n/]
 
 With delayed allocation enabled, the above scenario changes to look like this:
 
@@ -83,6 +84,7 @@ PUT _all/_settings
   }
 }
 ```
+%  TEST[s/^/PUT test\n/]
 
 You can reset the timeout as soon as the missing shards have started to recover.
 

deploy-manage/maintenance/add-and-remove-elasticsearch-nodes.md

@@ -107,6 +107,7 @@ POST /_cluster/voting_config_exclusions?node_names=node_name
 # auto-reconfiguration up to one minute
 POST /_cluster/voting_config_exclusions?node_names=node_name&timeout=1m
 ```
+%  TEST[skip:this would break the test cluster if executed]
 
 The nodes that should be added to the exclusions list are specified by name using the `?node_names` query parameter, or by their persistent node IDs using the `?node_ids` query parameter. If a call to the voting configuration exclusions API fails, you can safely retry it. Only a successful response guarantees that the node has actually been removed from the voting configuration and will not be reinstated. If the elected master node is excluded from the voting configuration then it will abdicate to another master-eligible node that is still in the voting configuration if such a node is available.
 

deploy-manage/monitor/logging-configuration/elasticsearch-deprecation-logs.md

@@ -259,6 +259,7 @@ You can identify what is triggering deprecated functionality if `X-Opaque-Id` wa
   "node.id": "D7fUYfnfTLa2D7y-xw6tZg"
 }
 ```
+%  NOTCONSOLE
 
 Deprecation logs can be indexed into `.logs-deprecation.elasticsearch-default` data stream `cluster.deprecation_indexing.enabled` setting is set to true.
 

deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md

@@ -256,6 +256,7 @@ You can identify what is triggering deprecated functionality if `X-Opaque-Id` wa
   "node.id": "D7fUYfnfTLa2D7y-xw6tZg"
 }
 ```
+%  NOTCONSOLE
 
 Deprecation logs can be indexed into `.logs-deprecation.elasticsearch-default` data stream `cluster.deprecation_indexing.enabled` setting is set to true.
 

deploy-manage/monitor/logging-configuration/update-elasticsearch-logging-levels.md

@@ -259,6 +259,7 @@ You can identify what is triggering deprecated functionality if `X-Opaque-Id` wa
   "node.id": "D7fUYfnfTLa2D7y-xw6tZg"
 }
 ```
+%  NOTCONSOLE
 
 Deprecation logs can be indexed into `.logs-deprecation.elasticsearch-default` data stream `cluster.deprecation_indexing.enabled` setting is set to true.