# Override file for elasticsearch.yml

**URL:** <https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170>\
**Category:** Elasticsearch\
**Created:** [June 23, 2015, 10:04am UTC](https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170 "2015-06-23T10:04:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rrva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rrva/32/43888_2.png) [@rrva](https://discuss.elastic.co/u/rrva)\
**Post date:** [June 23, 2015, 10:04am UTC](https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170/1 "2015-06-23T10:04:21Z")

</div>

Is it possible to make elasticsearch first read elasticsearch.yml and then apply a elasticsearch-local.yml which overrides any setting found in elasticsearch.yml ? That way I can have any local changes not be overridden once i rewrite elasticsearch.yml

---

<div class="post-metadata">

**Author:** ![rrva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rrva/32/43888_2.png) [@rrva](https://discuss.elastic.co/u/rrva)\
**Post date:** [June 23, 2015, 10:26am UTC](https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170/2 "2015-06-23T10:26:48Z")

</div>

Also, is there a way to dump all config settings in a running process which deviate from the default?

---

<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:** [June 23, 2015, 10:42am UTC](https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170/3 "2015-06-23T10:42:26Z")

</div>

Nope, it's all or nothing for the config.

[This](https://github.com/elastic/elasticsearch/issues/10713) may relate to your second question.

---

<div class="post-metadata">

**Author:** ![rrva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rrva/32/43888_2.png) [@rrva](https://discuss.elastic.co/u/rrva)\
**Post date:** [June 23, 2015, 11:39am UTC](https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170/4 "2015-06-23T11:39:54Z")

</div>

Is there any workaround to handle config overrides? yaml does not allow for include directives..

I have a script which produces a new elasticsearch.yml for a specific installation, and I do not want to in-place edit an existing file, but rather have some include mechanism

---

<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:** [June 23, 2015, 11:47am UTC](https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170/5 "2015-06-23T11:47:37Z")

</div>

This question is very familiar, did you ask this before?

However the answer is still no, you cannot do this natively.  
You may be able to with config management tools like Puppet or Chef.

---

<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 6, 2017, 12:05am UTC](https://discuss.elastic.co/t/override-file-for-elasticsearch-yml/24170/6 "2017-07-06T00:05:57Z")

</div>