# Automating ES template management using Logstash output **URL:** \ **Category:** Logstash\ **Created:** [November 18, 2019, 9:58am UTC](https://discuss.elastic.co/t/automating-es-template-management-using-logstash-output/208282 "2019-11-18T09:58:27Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![74db36a597f21b891b3f](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/74db36a597f21b891b3f/32/45367_2.png) [@74db36a597f21b891b3f](https://discuss.elastic.co/u/74db36a597f21b891b3f)\ **Post date:** [November 18, 2019, 9:58am UTC](https://discuss.elastic.co/t/automating-es-template-management-using-logstash-output/208282/1 "2019-11-18T09:58:27Z")
Hello there. I'm a little bit confused in finding a way to manage ES templates. Now I edit them manually via Cerebro. But I'd like to store it in some storage like git and push them automatically. I know that Logstash output has ability to push templates, but have a few questions regarding this feature. 1. I have several template with different order. Can I push them in one output block, or I should create several output blocks one per template? 2. I also have may outputs in my logstash config with different index names. Should I pass templates with every output? 3. Let's assume that I made some change in templates. I want new indices to be created with new mappings. How can I make sure that templates will be loaded into ES before data will actually flow? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 16, 2019, 9:58am UTC](https://discuss.elastic.co/t/automating-es-template-management-using-logstash-output/208282/2 "2019-12-16T09:58:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.