Skip to content

Commit 1c4069c

Browse files
authored
[DOCS] Fix wildcard default for delete index in 7.x branches (#76922) (#76927)
In 7.x versions, the `action.destructive_requires_name` cluster setting defaults to `false`. The 7.x backports of #74674 introduced a docs bug that indicate the setting defaults to `true`. This reverts the related changes.
1 parent 4624a9e commit 1c4069c

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/reference/indices/delete-index.asciidoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -33,11 +33,11 @@ or `manage` <<privileges-list-indices,index privilege>> for the target index.
3333
(Required, string) Comma-separated list of indices to delete. You cannot specify
3434
<<alias,index aliases>>.
3535

36-
By default, this parameter does not support wildcards (`*`) or `_all`. To use
37-
wildcards or `_all`, change the `action.destructive_requires_name` setting to
38-
`false`. You can update this setting in the `elasticsearch.yml` file or using
39-
the <<cluster-update-settings,cluster update settings>> API. Wildcard patterns
40-
only match open, concrete indices.
36+
To delete all indices, use `_all` or `*` . To disallow the deletion of indices
37+
with `_all` or wildcard expressions, change the
38+
`action.destructive_requires_name` cluster setting to `true`. You can update
39+
this setting in the `elasticsearch.yml` file or using the
40+
<<cluster-update-settings,cluster update settings>> API.
4141

4242
NOTE: You cannot delete the current write index of a data stream. To delete the
4343
index, you must <<data-streams-rollover,roll over>> the data stream so a new

0 commit comments

Comments
 (0)