cameronkerrnz / logstash-plugin-dev Goto Github PK

Well described in jruby/jruby#6950 (comment) . I now see a comment about this in the Dockerfile implying that the Script Engine works in 11. Then I assume the bug still exists here. Hopefully will resolve my testing issue.

Hi there,

first of all thanks for this project, it seems like you are filling a gap there cause I was not be able to find any docker image for building logstash plugins.

I am trying to build locally the logstash-output-mongo plugin and I found the following:

$ docker run --rm -it -v ${PWD}:/work cameronkerrnz/logstash-plugin-dev:7.9 bundle
/opt/jruby/bin/bundle: line 9: require: command not found
/opt/jruby/bin/bundle: line 11: version: command not found
/opt/jruby/bin/bundle: bundle: line 15: syntax error near unexpected token `('
/opt/jruby/bin/bundle: bundle: line 15: `  str = str.dup.force_encoding("BINARY") if str.respond_to? :force_encoding'

Am I doing the right thing?

Thanks again!

Hi @cameronkerrnz sorry I have another question here.

I am trying to debug the following problem:

$ bundle exec rspec spec/outputs/mongodb_update_spec.rb 
Sending Logstash logs to null which is now configured via log4j2.properties
Run options: exclude {:integration=>true, :redis=>true, :socket=>true, :performance=>true, :couchdb=>true, :elasticsearch=>true, :elasticsearch_secure=>true, :export_cypher=>true, :windows=>true}

As you can see though, I am not seeing the logs and I think I am missing some compilation issues.

Also Sending Logstash logs to null which is now configured via log4j2.properties is suspicious.

Do you know how I can enable logging when testing by any chance?