# Destructive\_requires\_name override **URL:** \ **Category:** Elasticsearch\ **Created:** [April 6, 2016, 2:12am UTC](https://discuss.elastic.co/t/destructive-requires-name-override/46462 "2016-04-06T02:12:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![podollb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/podollb/32/3703_2.png) [@podollb](https://discuss.elastic.co/u/podollb)\ **Post date:** [April 6, 2016, 2:12am UTC](https://discuss.elastic.co/t/destructive-requires-name-override/46462/1 "2016-04-06T02:12:19Z")
I have `action.destructive_requires_name: true` set in my config to disallow operations on `_all` and wildcards, but in certain situations I still want to do that (for things like `closing` all indices before a restore). So I was wondering if there was a way to override that via query params? Or is there another configuration I could use that doesn't necessarily prevent from doing it across the board, but is more fine grained (to disallow `_all` for "delete" but allows it on "close"). I'm guessing not (so I'll just script my solution by grabbing the index list and then issuing the close on each), but figured I'd ask. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 6, 2016, 3:07am UTC](https://discuss.elastic.co/t/destructive-requires-name-override/46462/2 "2016-04-06T03:07:56Z")
Nope. But you can provide multiple indices via `host:9200/index1,index2,otherindex/_blah`. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:02pm UTC](https://discuss.elastic.co/t/destructive-requires-name-override/46462/3 "2017-07-05T23:02:05Z")