Magnus Bäck

Yes, this would definitely be useful. Have you given any thoughts as to how this could be expressed in the testcase file? Field values with special meanings that LFV interprets,...

Instead of inventing our own language we should provide an ability to use jq to evaluate the JSON blob produced by Logstash, i.e. instead of diffing it against a JSON...

This is arguably a bug in Logstash, but if we can work around it that'd be great. Have you given any thought regarding how to deal with this? Would it...

Yes, Logstash behaves correctly but LFV doesn't. Here's 2.4.1 for reference: ```plain $ ~/src/logstash-filter-verifier/src/github.com/magnusbaeck/logstash-filter-verifier/logstash-filter-verifier --sockets roles/logstash-hub/templates/logstash/tests roles/logstash-hub/templates/logstash/*-filter.conf.j2 Use Unix domain sockets. ☐ Compare actual event with expected event from client-decoration.yaml:...

20 seconds to process a single test case file? That sounds very slow. But yes, I suspect lack of support for stdin would make use of drip hard. I suppose...

This would indeed be nice, but do you have any ideas of how to accomplish in a robust fashion without writing a full lexer and parser for Logstash's configuration language?...

Could you please provide a minimal example file that illustrates the problem?

Yes, could you please do that? I haven't experienced any problems with testcases being dropped.

Given the security implications of accessing (and executing) things over the network I think we should start with just supporting a local LFV daemon. How would the communication between the...

> I agree, as a start we should limit the usage to the same host (and exclude anything over the network). I assume, that if we really get the daemon...