Based on all the great work that @original-brownbear has done in tools/ingest-convertor it is time now to create a CLI tool that provides an end-user interface to move from ingest pipeline to LS config.
I propose two flavors to make it dead simple and easy for our users -- offline and an online.
defaults to localhost:9200. It then gets the json pipeline using the ES API call GET _ingest/pipeline/apache, stores it in memory or tmp location and then converts it using the utilities created.
Based on all the great work that @original-brownbear has done in
tools/ingest-convertor
it is time now to create a CLI tool that provides an end-user interface to move from ingest pipeline to LS config.I propose two flavors to make it dead simple and easy for our users -- offline and an online.
Offline
This would call the
ingest_pipeline_to_logstash()
js function as done in https://github.com/elastic/logstash/blob/master/tools/ingest-converter/src/main/java/org/logstash/ingest/Pipeline.javaWe can create all the heavy lifting in Java and just write a shell wrapper around it.
Online (Lower priority)
This assumes the user has access to the ES endpoint where the ingest pipeline is defined.
defaults to
localhost:9200
. It then gets the json pipeline using the ES API callGET _ingest/pipeline/apache
, stores it in memory or tmp location and then converts it using the utilities created.can accept optional ES config for credentials:
For this, maybe we can use the Java high-level client from ES (when it gets shipped)