The change here makes sure "es_host:port" is properly split into a { host: es_host, port: port } pair.
Elasticsearch gem not seeing a port: key will add the port: 9200 default and Manticore 0.8 appends the port part while building the URL.
The issue did reproduce with the added integration test (under SECURE_INTEGRATION) - we did not have testing setup with secured ES, the setup has been ~ copied from ES output plugin.
There's also some additional test targets to keep testing against previous ES and Manticore gem versions.
The change here makes sure "es_host:port" is properly split into a
{ host: es_host, port: port }pair. Elasticsearch gem not seeing aport:key will add theport: 9200default and Manticore 0.8 appends the port part while building the URL.The issue did reproduce with the added integration test (under
SECURE_INTEGRATION) - we did not have testing setup with secured ES, the setup has been ~ copied from ES output plugin.There's also some additional test targets to keep testing against previous ES and Manticore gem versions.
CI :red_circle: are caused by https://github.com/logstash-plugins/logstash-filter-elasticsearch/issues/157 (and https://github.com/logstash-plugins/logstash-input-elasticsearch/issues/165)