Skip to content

Commit c18708e

Browse files
colleenmcginniscolleenmcginnis
committed
clean up
1 parent 9f52f46 commit c18708e

25 files changed

+116
-45
lines changed

‎deploy-manage/autoscaling/autoscaling-deciders.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,7 @@ PUT /_autoscaling/policy/my_autoscaling_policy
8080
}
8181
}
8282
```
83+
% TEST
8384

8485
The API returns the following result:
8586

@@ -157,6 +158,7 @@ PUT /_autoscaling/policy/my_autoscaling_policy
157158
}
158159
}
159160
```
161+
% TEST
160162

161163
The API returns the following result:
162164

@@ -213,6 +215,7 @@ PUT /_autoscaling/policy/my_autoscaling_policy
213215
}
214216
}
215217
```
218+
% TEST
216219

217220
The API returns the following result:
218221

‎deploy-manage/tools/snapshot-and-restore/google-cloud-storage-repository.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,6 @@ PUT _snapshot/my_gcs_repository
9191
}
9292
```
9393
% TEST[skip:we don’t have gcs setup while testing this]
94-
% TEST[skip:we don’t have gcs setup while testing this]
9594

9695
The `credentials_file` settings are [reloadable](../../security/secure-settings.md#reloadable-secure-settings). You can define these settings before the node is started, or call the [Nodes reload secure settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-reload-secure-settings) after the settings are defined to apply them to a running node.
9796

@@ -120,6 +119,7 @@ PUT _snapshot/my_gcs_repository
120119
}
121120
}
122121
```
122+
% TEST[skip:we don’t have gcs setup while testing this]
123123

124124
Some settings are sensitive and must be stored in the [Elasticsearch keystore](../../security/secure-settings.md). This is the case for the service account file:
125125

‎deploy-manage/tools/snapshot-and-restore/restore-snapshot.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,6 @@ DELETE my-index
9393
DELETE _data_stream/logs-my_app-default
9494
```
9595
% TEST[setup:setup-snapshots]
96-
% TEST[setup:setup-snapshots]
9796
In the restore request, explicitly specify any indices and data streams to restore.
9897

9998
```console
@@ -118,7 +117,8 @@ POST _snapshot/my_repository/my_snapshot_2099.05.06/_restore
118117
{
119118
"indices": "my-index,logs-my_app-default",
120119
"rename_pattern": "(.+)",
121-
"rename_replacement": "restored-$1"
120+
"rename_replacement": "restored-
121+
If the rename options produce two or more indices or data streams with the same name, the restore operation fails."
122122
}
123123
```
124124
% TEST[setup:setup-snapshots]

‎deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -255,6 +255,7 @@ Use the dot notations to refer to nested fields in more complex documents. For e
255255
}
256256
}
257257
```
258+
% NOTCONSOLE
258259

259260
The following role definition enables only read access to the customer `handle` field:
260261

‎deploy-manage/users-roles/cluster-or-deployment-auth/jwt.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -205,6 +205,7 @@ Header: {"typ":"JWT","alg":"HS256"}
205205
Claims: {"aud":"aud8","sub":"security_test_user","iss":"iss8","exp":4070908800,"iat":946684800}
206206
Signature: UnnFmsoFKfNmKMsVoDQmKI_3-j95PCaKdgqqau3jPMY
207207
```
208+
% NOTCONSOLE
208209

209210
This example illustrates a partial decoding of a JWT. The validity period is from 2000 to 2099 (inclusive), as defined by the issue time (`iat`) and expiration time (`exp`). JWTs typically have a validity period shorter than 100 years, such as 1-2 hours or 1-7 days, not an entire human life.
210211

@@ -396,6 +397,7 @@ $$$jwt-auth-shared-secret-scheme-example$$$
396397
```sh
397398
curl -s -X GET -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhdWQiOlsiZXMwMSIsImVzMDIiLCJlczAzIl0sInN1YiI6InVzZXIyIiwiaXNzIjoibXktaXNzdWVyIiwiZXhwIjo0MDcwOTA4ODAwLCJpYXQiOjk0NjY4NDgwMCwiZW1haWwiOiJ1c2VyMkBzb21ldGhpbmcuZXhhbXBsZS5jb20ifQ.UgO_9w--EoRyUKcWM5xh9SimTfMzl1aVu6ZBsRWhxQA" -H "ES-Client-Authentication: sharedsecret test-secret" https://localhost:9200/_security/_authenticate
398399
```
400+
% NOTCONSOLE
399401

400402
The response includes the user who submitted the request (`user2`), including the `jwt_role1` role that you mapped to this user in the JWT realm:
401403

@@ -412,6 +414,7 @@ If you want to specify a request as the `run_as` user, include the `es-security-
412414
```sh
413415
curl -s -X GET -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhdWQiOlsiZXMwMSIsImVzMDIiLCJlczAzIl0sInN1YiI6InVzZXIyIiwiaXNzIjoibXktaXNzdWVyIiwiZXhwIjo0MDcwOTA4ODAwLCJpYXQiOjk0NjY4NDgwMCwiZW1haWwiOiJ1c2VyMkBzb21ldGhpbmcuZXhhbXBsZS5jb20ifQ.UgO_9w--EoRyUKcWM5xh9SimTfMzl1aVu6ZBsRWhxQA" -H "ES-Client-Authentication: sharedsecret test-secret" -H "es-security-runas-user: user123_runas" https://localhost:9200/_security/_authenticate
414416
```
417+
% NOTCONSOLE
415418

416419
In the response, you’ll see that the `user123_runas` user submitted the request, and {{es}} used the `jwt_role1` role:
417420

@@ -530,12 +533,14 @@ The following header settings are for an {{es}} client.
530533
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJpc3M4IiwiYXVkIjoiYXVkOCIsInN1YiI6InNlY3VyaXR5X3Rlc3RfdXNlciIsImV4cCI6NDA3MDkwODgwMCwiaWF0Ijo5NDY2ODQ4MDB9.UnnFmsoFKfNmKMsVoDQmKI_3-j95PCaKdgqqau3jPMY
531534
ES-Client-Authentication: SharedSecret client-shared-secret-string
532535
```
536+
% NOTCONSOLE
533537

534538
You can use this header in a `curl` request to make an authenticated call to {{es}}. Both the bearer token and the client authorization token must be specified as separate headers with the `-H` option:
535539

536540
```sh
537541
curl -s -X GET -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJpc3M4IiwiYXVkIjoiYXVkOCIsInN1YiI6InNlY3VyaXR5X3Rlc3RfdXNlciIsImV4cCI6NDA3MDkwODgwMCwiaWF0Ijo5NDY2ODQ4MDB9.UnnFmsoFKfNmKMsVoDQmKI_3-j95PCaKdgqqau3jPMY" -H "ES-Client-Authentication: SharedSecret client-shared-secret-string" https://localhost:9200/_security/_authenticate
538542
```
543+
% NOTCONSOLE
539544

540545
If you used role mapping in the JWT realm, the response includes the user’s `username`, their `roles`, metadata about the user, and the details about the JWT realm itself.
541546

‎deploy-manage/users-roles/cluster-or-deployment-auth/native.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,7 @@ POST /_security/user/user1/_password
9090
"password" : "new-test-password"
9191
}
9292
```
93+
% TEST[continued]
9394

9495
For more information and examples, see [Users](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-security).
9596

‎explore-analyze/alerts-cases/watcher/watch-cluster-status.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,6 @@ GET .watcher-history*/_search?pretty
146146
}
147147
```
148148
% TEST[continued]
149-
% TEST[continued]
150149

151150
## Take action [health-take-action]
152151

@@ -223,6 +222,7 @@ GET .watcher-history*/_search?pretty
223222
}
224223
}
225224
```
225+
% TEST[continued]
226226

227227
## Delete the watch [health-delete]
228228

‎manage-data/data-store/data-streams/run-downsampling-manually.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -257,7 +257,6 @@ You can use the search API to check if the documents have been indexed correctly
257257
```console
258258
GET /my-data-stream/_search
259259
```
260-
% TEST[skip:Because we’ve skipped the previous steps]
261260
% TEST[continued]
262261

263262
Run the following aggregation on the data to calculate some interesting statistics:
@@ -423,6 +422,7 @@ Re-run the earlier search query (note that when querying downsampled indices the
423422
```console
424423
GET /my-data-stream/_search
425424
```
425+
% TEST[skip:Because we’ve skipped the previous steps]
426426

427427
The TSDS with the new downsampled backing index contains just one document. For counters, this document would only have the last value. For gauges, the field type is now `aggregate_metric_double`. You see the `min`, `max`, `sum`, and `value_count` statistics based off of the original sampled metrics:
428428

@@ -575,6 +575,7 @@ GET /my-data-stream/_search
575575
}
576576
}
577577
```
578+
% TEST[continued]
578579

579580
This example demonstrates how downsampling can dramatically reduce the number of documents stored for time series data, within whatever time boundaries you choose. It’s also possible to perform downsampling on already downsampled data, to further reduce storage and associated costs, as the time series data ages and the data resolution becomes less critical.
580581

‎manage-data/data-store/data-streams/run-downsampling-using-data-stream-lifecycle.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,6 @@ Now that you’ve created and added documents to the data stream, check to confi
230230
GET _data_stream
231231
```
232232
% TEST[skip: temporal_ranges and index names won’t match]
233-
% TEST[skip: temporal_ranges and index names won’t match]
234233

235234
If the data stream lifecycle policy has not yet been applied, your results will be like the following. Note the original `index_name`: `.ds-datastream-2024.04.29-000001`.
236235

@@ -287,7 +286,6 @@ Next, run a search query:
287286
```console
288287
GET datastream/_search
289288
```
290-
% TEST[continued]
291289
% TEST[skip: timestamp values won’t match]
292290

293291
The query returns your ten newly added documents.
@@ -332,6 +330,7 @@ By default, data stream lifecycle actions are executed every five minutes. Downs
332330
```console
333331
GET _data_stream
334332
```
333+
% TEST[skip: temporal_ranges and index names won’t match]
335334

336335
After the data stream lifecycle action was executed, original `.ds-datastream-2024.04.29-000001` index is replaced with a new, downsampled index, in this case `downsample-1h-.ds-datastream-2024.04.29-000001`.
337336

@@ -365,6 +364,7 @@ Run a search query on the datastream (note that when querying downsampled indice
365364
```console
366365
GET datastream/_search
367366
```
367+
% TEST[continued]
368368

369369
The new downsampled index contains just one document that includes the `min`, `max`, `sum`, and `value_count` statistics based off of the original sampled metrics.
370370

‎manage-data/data-store/data-streams/run-downsampling-with-ilm.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -254,7 +254,6 @@ Now that you’ve created and added documents to the data stream, check to confi
254254
GET _data_stream
255255
```
256256
% TEST[skip: The @timestamp value won’t match an accepted range in the TSDS]
257-
% TEST[skip: The @timestamp value won’t match an accepted range in the TSDS]
258257

259258
If the ILM policy has not yet been applied, your results will be like the following. Note the original `index_name`: `.ds-datastream-<timestamp>-000001`.
260259

@@ -305,7 +304,6 @@ Next, run a search query:
305304
```console
306305
GET datastream/_search
307306
```
308-
% TEST[continued]
309307
% TEST[skip: The @timestamp value won’t match an accepted range in the TSDS]
310308

311309
The query returns your ten newly added documents.
@@ -335,6 +333,7 @@ By default, index lifecycle management checks every ten minutes for indices that
335333
```console
336334
GET _data_stream
337335
```
336+
% TEST[skip: The @timestamp value won’t match an accepted range in the TSDS]
338337

339338
After the ILM policy has taken effect, the original `.ds-datastream-2022.08.26-000001` index is replaced with a new, downsampled index, in this case `downsample-6tkn-.ds-datastream-2022.08.26-000001`.
340339

@@ -366,6 +365,7 @@ Run a search query on the datastream (note that when querying downsampled indice
366365
```console
367366
GET datastream/_search
368367
```
368+
% TEST[continued]
369369

370370
The new downsampled index contains just one document that includes the `min`, `max`, `sum`, and `value_count` statistics based off of the original sampled metrics.
371371

0 commit comments

Comments
 (0)