# Elasticsearch Curator on Google Functions

**URL:** <https://discuss.elastic.co/t/elasticsearch-curator-on-google-functions/196034>\
**Category:** Elasticsearch\
**Tags:** curator\
**Created:** [August 21, 2019, 4:00am UTC](https://discuss.elastic.co/t/elasticsearch-curator-on-google-functions/196034 "2019-08-21T04:00:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ssharaf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ssharaf/32/48801_2.png) [@ssharaf](https://discuss.elastic.co/u/ssharaf)\
**Post date:** [August 21, 2019, 4:00am UTC](https://discuss.elastic.co/t/elasticsearch-curator-on-google-functions/196034/1 "2019-08-21T04:00:58Z")

</div>

Hi,

I am writing a Python script to delete Metricbeat indices older than certain days using ES Curator. I could successfully install the curator on my machine and run the code.

I want to deploy the script to Google Functions and schedule it to run it daily. When trying to deploy the code to Google Functions, the deployment fails due to the following error:

`ERROR: (gcloud.functions.deploy) OperationError: code=3, message=Build failed: {"error": {"canonicalCode": "INVALID_ARGUMENT", "errorMessage": "`pip\_download\_wheels`had stderr output:\nCommand \"python setup.py egg_info\" failed with error code 1 in /tmp/pip-wheel-bpfumh67/elasticsearch-curator/\n\nerror:`pip\_download\_wheels`returned code: 1", "errorType": "InternalError", "errorId": "1F88AD90"}}`

As I could understand from the error, it is unable to install `elasticsearch-curator` when `pip` is installing dependencies. Is there a way to overcome this issue?

Thank you.

---

<div class="post-metadata">

**Author:** ![aravindputrevu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aravindputrevu/32/24816_2.png) [@aravindputrevu](https://discuss.elastic.co/u/aravindputrevu)\
**Post date:** [August 21, 2019, 4:13am UTC](https://discuss.elastic.co/t/elasticsearch-curator-on-google-functions/196034/2 "2019-08-21T04:13:56Z")

</div>

Nice idea!

But we have thought about it and implemented the same.

Please refer [Index Lifecycle Management](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/getting-started-index-lifecycle-management.html)

--  
Aravind

---

<div class="post-metadata">

**Author:** ![ssharaf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ssharaf/32/48801_2.png) [@ssharaf](https://discuss.elastic.co/u/ssharaf)\
**Post date:** [August 21, 2019, 5:15am UTC](https://discuss.elastic.co/t/elasticsearch-curator-on-google-functions/196034/3 "2019-08-21T05:15:48Z")

</div>

Hi Aravind

Thank you for your reply. I could successfully do it using ILM. Many thanks.

---

<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:** [September 18, 2019, 5:15am UTC](https://discuss.elastic.co/t/elasticsearch-curator-on-google-functions/196034/4 "2019-09-18T05:15:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.