# Ingest pipeline version control and deployment
**URL:** https://discuss.elastic.co/t/ingest-pipeline-version-control-and-deployment/234493
**Category:** Elasticsearch
**Created:** [May 27, 2020, 8:54am UTC](https://discuss.elastic.co/t/ingest-pipeline-version-control-and-deployment/234493 "2020-05-27T08:54:23Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@whatgeorgemade](https://discuss.elastic.co/u/whatgeorgemade)
#### Post date: [May 27, 2020, 8:54am UTC](https://discuss.elastic.co/t/ingest-pipeline-version-control-and-deployment/234493/1 "2020-05-27T08:54:23Z")
I'm wondering how other people deal with managing their ingest pipelines in terms of version control and deployment to the cluster.
I put pipeline definitions in Git so I can track the changes and, more importantly, the reason for the changes.
I still haven't found a nice way to automatically deploy new versions of pipelines. I cobbled a script together that will iterate over the definitions and push them to the cluster but it's rough and not very robust. I'd like to make some improvements to it but wanted to see if anyone is using an existing solution first.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 24, 2020, 8:54am UTC](https://discuss.elastic.co/t/ingest-pipeline-version-control-and-deployment/234493/2 "2020-06-24T08:54:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.