Skip to content

Commit cd8e1e6

Browse files
docs: fix numbering in restore-snapshot.asciidoc (#103769) (#103851)
* docs: fix numbering in restore-snapshot.asciidoc Fix numbering in "Restore an entire cluster" section. Remove "3." for "Universal Profiling" and add "3." just before "If you use Elasticsearch security features" * Keep ID, fix list rendering --------- Co-authored-by: Fabien Baligand <[email protected]>
1 parent 78b990c commit cd8e1e6

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

docs/reference/snapshot-restore/restore-snapshot.asciidoc

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -359,12 +359,7 @@ POST _watcher/_start
359359
----
360360
// TEST[continued]
361361
////
362-
--
363-
364362

365-
. {blank}
366-
+
367-
--
368363
* Universal Profiling
369364
+
370365
Check if Universal Profiling index template management is enabled:
@@ -385,22 +380,25 @@ PUT _cluster/settings
385380
}
386381
}
387382
----
383+
--
388384

389-
[[restore-create-file-realm-user]]
390-
If you use {es} security features, log in to a node host, navigate to the {es}
391-
installation directory, and add a user with the `superuser` role to the file
392-
realm using the <<users-command,`elasticsearch-users`>> tool.
385+
. [[restore-create-file-realm-user]]If you use {es} security features, log in to
386+
a node host, navigate to the {es} installation directory, and add a user with
387+
the `superuser` role to the file realm using the
388+
<<users-command,`elasticsearch-users`>> tool.
389+
+
393390

394391
For example, the following command creates a user named `restore_user`.
392+
+
395393

396394
[source,sh]
397395
----
398396
./bin/elasticsearch-users useradd restore_user -p my_password -r superuser
399397
----
398+
+
400399

401400
Use this file realm user to authenticate requests until the restore operation is
402401
complete.
403-
--
404402

405403
. Use the <<cluster-update-settings,cluster update settings API>> to set
406404
<<action-destructive-requires-name,`action.destructive_requires_name`>> to

0 commit comments

Comments
 (0)