Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unnecessary Dependency? #210

Open
abates opened this issue Sep 18, 2017 · 2 comments
Open

Unnecessary Dependency? #210

abates opened this issue Sep 18, 2017 · 2 comments

Comments

@abates
Copy link

abates commented Sep 18, 2017

I'm curious why logstash-core-plugin-api is included as a runtime dependency in the gemspec?

s.add_runtime_dependency "logstash-core-plugin-api", ">= 1.60", "<= 2.99"

I don't see that this gem is actually included anywhere. I wanted to write a quick script to test some grok patterns using the baseline patterns in logstash-patterns-core. However, since I don't use jruby and logstash-core-plugin-api has depdencies for several jruby gems I can't use logstash-patterns-core directly.

Can the runtime dependency be removed?

@jsvd
Copy link
Member

jsvd commented Sep 18, 2017

Indeed we could remove the dependency here. The logstash-core-plugin-api helps logstash know which plugins work with which versions of logstash-core without having to update all plugins with new releases of core.

in this case, the logstash-patterns-core ruby code has a very tiny piece of code to interact with core..what do you think @ph?

@ph
Copy link
Contributor

ph commented Sep 18, 2017

I have more interrogation:

  • Currently, this plugin (or raw text) have the really little dependency on the core.
  • Maybe core should provide a more official API to change load path?
  • Maybe we should depend on the logstash-filter-grok instead?
  • Why this code isn't in the grok filter? Do we need this level of indirection?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants