Browse Source

Add breaking change notice for action.destructive_requires_name (#71007)

* Add breaking change notice for action.destructive_requires_name
William Brafford 4 years ago
parent
commit
6b349af7d9
1 changed files with 19 additions and 0 deletions
  1. 19 0
      docs/reference/migration/migrate_8_0/settings.asciidoc

+ 19 - 0
docs/reference/migration/migrate_8_0/settings.asciidoc

@@ -166,3 +166,22 @@ Discontinue use of the removed settings. If needed, use
 `gateway.expected_data_nodes` or `gateway.recover_after_data_nodes` to defer
 cluster recovery pending a certain number of data nodes.
 ====
+
+.By default, destructive index actions do not allow wildcards.
+[%collapsible]
+====
+*Details* +
+The default value of the setting `action.destructive_requires_name` changes from `false`
+to `true` in {es} 8.0.0.
+
+In previous versions, the default setting allowed users to use wildcard
+patterns to delete, close, or change index blocks on indices. In order
+to prevent the accidental deletion of indices that happen to match a
+wildcard pattern, we now require, by default, that any such destructive
+operation explicitly name the indices it intends to modify.
+
+*Impact* +
+If you would like to use wildcard patterns for destructive actions, set
+`action.destructive_requires_name` to `false` using the <<cluster-update-settings,
+cluster settings>> API.
+====