# Elasticsearch config parsed in Python **URL:** \ **Category:** Elasticsearch\ **Created:** [January 22, 2019, 4:28am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147 "2019-01-22T04:28:09Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![merceskoba](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@merceskoba](https://discuss.elastic.co/u/merceskoba)\ **Post date:** [January 22, 2019, 4:28am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/1 "2019-01-22T04:28:09Z")
Hello guys So, i have a problem to maintain elasticsearch config in production. There are so many changes to elasticsearch config. So, i need to change the `discovery.zen.ping.unicast.hosts: ["1.1.1.2"]` to be `discovery.zen.ping.unicast.hosts: ["1.1.1.2", "1.1.1.3]` if i want to add new instance. This is the repetitive work. Do you have any idea how do i change all config for each elasticsearch instance easily ? ---
**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:** [January 22, 2019, 5:03am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/2 "2019-01-22T05:03:21Z")
If you are using python then you should use our library, which will handle nodes changes as long as it can reach one node in the cluster. ---
**Author:** ![merceskoba](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@merceskoba](https://discuss.elastic.co/u/merceskoba)\ **Post date:** [January 22, 2019, 7:03am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/3 "2019-01-22T07:03:56Z")
do you have the example to use it for setting configuration ? I have searched in google, and always find unrelated case ---
**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:** [January 22, 2019, 10:43pm UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/4 "2019-01-22T22:43:38Z")
The docs for the client (which ever one you are using) are the best place for that. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 23, 2019, 3:20am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/5 "2019-01-23T03:20:56Z")
Are you using any orchestration management tool, e.g. Ansible, Chef or Puppet? This is often how configurations are managed at scale. ---
**Author:** ![merceskoba](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@merceskoba](https://discuss.elastic.co/u/merceskoba)\ **Post date:** [January 24, 2019, 7:05am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/6 "2019-01-24T07:05:28Z")
Ansible... hmm... yeah yeah... Ansible can do this But, Ansible is not available for developer in my company. Ansible is for system engineer only. So, we can't be available for them 24/7 ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 24, 2019, 7:18am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/7 "2019-01-24T07:18:37Z")
Ansible is a good tool for the job. If you for some internal policy reasons can not use it I guess you will need to create your own solution, which to me sounds a lot like reinventing the wheel. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 21, 2019, 7:18am UTC](https://discuss.elastic.co/t/elasticsearch-config-parsed-in-python/165147/8 "2019-02-21T07:18:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.