Closed purbon closed 8 years ago
@jsvd can you let me know your thought on this backport?
Code LGTM, but we need to address the concurrent-ruby version problem before merging.. so if logstash-core is <=1.5.5 concurrent-ruby needs to be 0.9.1, but if > 1.5.5 then 0.9.2?
@jsvd as it's right now the gemfile is only helping on development environment. It will be harmless when installing the plugin/gem. what do you think?
but doing bundle install && bundle exec rspec will break as soon as 1.5.6 is released, right? maybe we can pin down the logstash-core version only in the group?
well I guess as soon as 1.5.6 gets released we don't need this anymore. what do you think?
ahh because 1.5.6 pins a specific version of concurrent-ruby instead of ~0.9.1? that still means we'll need to come to this plugin and remove the group definition, right?
+1 on removing the concurrent-ruby pinning otherwise LGTM
ah and please change the logstash-core dependency to < 2.0.0.alpha0 ?
works for me, thanks for your feedback.
Fixes #19 and #22 for the core-api-v1 (aka 1.x logstash-core) series of plugins.