# Getting Parameters from Configuration

**URL:** <https://discuss.elastic.co/t/getting-parameters-from-configuration/49757>\
**Category:** Elasticsearch\
**Created:** [May 11, 2016, 11:37am UTC](https://discuss.elastic.co/t/getting-parameters-from-configuration/49757 "2016-05-11T11:37:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rjperes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjperes/32/8351_2.png) [@rjperes](https://discuss.elastic.co/u/rjperes)\
**Post date:** [May 11, 2016, 11:37am UTC](https://discuss.elastic.co/t/getting-parameters-from-configuration/49757/1 "2016-05-11T11:37:35Z")

</div>

Hi!

Would it make sense to have the capability to store parameter values in a configuration file (elasticsearch.yml or other)? This way we wouldn't need to be passing values explicitly, but instead rely on configured ones.

This could be implemented either having a special syntax for parameters, like:

"params": {  
"mykey": "$configurationkey"  
}

or something else:

"configParams": ["mykey"]

What do you think?  
Thanks,

RP

---

<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:** [May 12, 2016, 12:25am UTC](https://discuss.elastic.co/t/getting-parameters-from-configuration/49757/2 "2016-05-12T00:25:02Z")

</div>

What's your vision here, what does this solve?

---

<div class="post-metadata">

**Author:** ![rjperes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rjperes/32/8351_2.png) [@rjperes](https://discuss.elastic.co/u/rjperes)\
**Post date:** [May 12, 2016, 8:24am UTC](https://discuss.elastic.co/t/getting-parameters-from-configuration/49757/3 "2016-05-12T08:24:18Z")

</div>

Hi, Mark!

IMO, It would make it easy to deploy and change configuration values. Yes, I know they can be stored in a client application as well, but this way it would make it easier to have multiple agnostic clients running queries with the same parameters (or, at least, default parameters), that admins could easily change.

RP

---

<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:52pm UTC](https://discuss.elastic.co/t/getting-parameters-from-configuration/49757/4 "2017-07-05T22:52:10Z")

</div>