# Is there a way to rename an ingest pipeline **URL:** \ **Category:** Elasticsearch\ **Created:** [April 2, 2020, 8:25am UTC](https://discuss.elastic.co/t/is-there-a-way-to-rename-an-ingest-pipeline/226173 "2020-04-02T08:25:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![A\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_b/32/17104_2.png) [@A\_B](https://discuss.elastic.co/u/A_B)\ **Post date:** [April 2, 2020, 8:25am UTC](https://discuss.elastic.co/t/is-there-a-way-to-rename-an-ingest-pipeline/226173/1 "2020-04-02T08:25:16Z")
Hello all, I found nothing on this searching the forum so opening a new topic. I also found nothing suggesting this would be possible in the comprehensive official documentation but I thought I would ask anyway 😃 Is it possible to rename an Elasticsearch ingest pipeline? The reason why I am asking is that I would like to start to make use of these but I am not really using Elastic default naming schemes. I use Elastic Stack for centralized logging. I was hoping that I could use names like `haproxy` or `nginx-access` for ingest pipelines instead of `filebeat-7.5.2-haproxy-log-pipeline` or `filebeat-7.5.2-nginx-access-default` whihc are the names Filebeat created for me. As I'm writing I realize that maybe there is a way to tell Filebeat what name to use for the pipeline it is creating. The original question still stands though. I quite regularly change my mind when it comes to things I name. Usually the first attempt turns out to be _not that great_ 😬 Any comments and suggestions are welcome 🙂 ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [April 2, 2020, 8:40am UTC](https://discuss.elastic.co/t/is-there-a-way-to-rename-an-ingest-pipeline/226173/2 "2020-04-02T08:40:42Z")
I'm curious about the use case. Why do you want to do that? ---
**Author:** ![A\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_b/32/17104_2.png) [@A\_B](https://discuss.elastic.co/u/A_B)\ **Post date:** [April 9, 2020, 12:27pm UTC](https://discuss.elastic.co/t/is-there-a-way-to-rename-an-ingest-pipeline/226173/3 "2020-04-09T12:27:33Z")
Hi @dadoonet, when you put it like that, I can't think of any really good examples of use cases. As I have Puppet to manage all my configs, if the name is a bit longer than I would prefer it to be, it is not really a problem. Having said all that, I still think it could be useful at some point to rename or copy a pipeline 🙂 ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [April 9, 2020, 2:06pm UTC](https://discuss.elastic.co/t/is-there-a-way-to-rename-an-ingest-pipeline/226173/4 "2020-04-09T14:06:42Z")
Well. It can be easy IMO to run a: ```auto GET /_pipeline/oldname PUT /_pipeline/newname { /* CONTENT FROM PREVIOUS REQUEST HERE */ } DELETE /_pipeline/oldname ``` Should be easy, no? ---
**Author:** ![A\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_b/32/17104_2.png) [@A\_B](https://discuss.elastic.co/u/A_B)\ **Post date:** [April 9, 2020, 2:07pm UTC](https://discuss.elastic.co/t/is-there-a-way-to-rename-an-ingest-pipeline/226173/5 "2020-04-09T14:07:52Z")
True, that seems like a pretty elegant solution 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 7, 2020, 2:08pm UTC](https://discuss.elastic.co/t/is-there-a-way-to-rename-an-ingest-pipeline/226173/6 "2020-05-07T14:08:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.