# Testable config changes

**URL:** <https://discuss.elastic.co/t/testable-config-changes/8915>\
**Category:** Elasticsearch\
**Created:** [September 3, 2012, 12:01am UTC](https://discuss.elastic.co/t/testable-config-changes/8915 "2012-09-03T00:01:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richo\_Healey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richo_healey/32/2572_2.png) [@Richo\_Healey](https://discuss.elastic.co/u/Richo_Healey)\
**Post date:** [September 3, 2012, 12:01am UTC](https://discuss.elastic.co/t/testable-config-changes/8915/1 "2012-09-03T00:01:59Z")

</div>

Hi Guys,

We're using ElasticSearch in production, with a view to managing it with  
Babushka[1](https://babushka.me). Our issue is that Babushka hinges on the notion of testable  
state, which causes issues for us, as if we push config to a database with  
a PUT query, a GET to the same URI doesn't yield the same configuration.

Is there a way to get that behaviour, or a clear specification of the  
transform so that we can perform it inside our deps?

Cheers

Richo

--

---

<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, 3:14am UTC](https://discuss.elastic.co/t/testable-config-changes/8915/2 "2017-07-06T03:14:18Z")

</div>

Closed on July 6, 2017, 3:14am UTC