# Better protection against typo in curator config file

**URL:** <https://discuss.elastic.co/t/better-protection-against-typo-in-curator-config-file/54235>\
**Category:** Elasticsearch\
**Created:** [June 29, 2016, 5:40am UTC](https://discuss.elastic.co/t/better-protection-against-typo-in-curator-config-file/54235 "2016-06-29T05:40:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hongyuan1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hongyuan1306/32/34868_2.png) [@hongyuan1306](https://discuss.elastic.co/u/hongyuan1306)\
**Post date:** [June 29, 2016, 5:40am UTC](https://discuss.elastic.co/t/better-protection-against-typo-in-curator-config-file/54235/1 "2016-06-29T05:40:08Z")

</div>

I am a new user to curator and with the latest version of curator (4.0.0) I started with the following action config:

```
actions:
  1:
    action: delete_indices
    fitlers:
    - filtertype: pattern
      kind: prefix
      value: logstash-
    - filtertype: age
      source: name
      timestring: '%Y.%m.%d'
      direction: older
      unit: days
      unit_count: 5

```

Instead of 'filters' i typed in 'fitlers', which is a fairly common error to make.

As a result, **all** my indices in elastics are removed. And it took me some time to figure out why this happened.

I would suggest that curator provide better protection against this sort of disaster. For example, when unrecognized options are encountered, an error shall be raised.

---

<div class="post-metadata">

**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:** [July 1, 2016, 4:05am UTC](https://discuss.elastic.co/t/better-protection-against-typo-in-curator-config-file/54235/2 "2016-07-01T04:05:10Z")

</div>

I'd recommend you raise this as an issue against the Curator repo - [https://github.com/elastic/curator/issues](https://github.com/elastic/curator/issues)

---

<div class="post-metadata">

**Author:** ![hongyuan1306](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hongyuan1306/32/34868_2.png) [@hongyuan1306](https://discuss.elastic.co/u/hongyuan1306)\
**Post date:** [July 1, 2016, 4:40am UTC](https://discuss.elastic.co/t/better-protection-against-typo-in-curator-config-file/54235/3 "2016-07-01T04:40:07Z")

</div>

Thanks, submitted as [https://github.com/elastic/curator/issues/674](https://github.com/elastic/curator/issues/674)

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [July 1, 2016, 1:41pm UTC](https://discuss.elastic.co/t/better-protection-against-typo-in-curator-config-file/54235/4 "2016-07-01T13:41:17Z")

</div>

For safety's sake, always use the `--dry-run` flag until you're sure your configuration is fully functional.

---

<div class="post-metadata">

**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, 10:38pm UTC](https://discuss.elastic.co/t/better-protection-against-typo-in-curator-config-file/54235/5 "2017-07-05T22:38:56Z")

</div>