Lucas Bremgartner

In regards to the "API" of the command `./logstash-filter-verifier` version 2 I have the following basic structure in mind: * The existing "standalone" mode for LFV: `./logstash-filter-verifier standalone`. This sub-command...

Here a proposal for the updated test case file format. There are no breaking changes, but two fields I would propose to be removed for the future (deprecated). All the...

> Looks good! The filter mock feature is really cool. I'll have use for that in one or two cases where I've currently used environment variables references in the config...

@nicolasreich Currently, there is no way to achieve this in daemon mode. We have a flag `--logstash-config`, which accepts a pure logstash config (without `pipeline.yml`), but this is not enough...

> It shouldn't be too hard to generate an HTML file with per-file stats and the configuration under test with non-covered filters marked with a different background color (similar to...

I am just hitting the exact same problem with the `logstash-filter-elasticsearch` plugin. Some days ago, I updated https://github.com/breml/logstash-config to better support altering of parsed Logstash configurations (before, some important fields...

A quick and dirty version of the code to remove filters by ID: ```Go import ( config "github.com/breml/logstash-config" "github.com/breml/logstash-config/ast" ) func removeFiltersByID(f *os.File, filename string, ids ...string) error { icfg,...

@nicolasreich there is currently some work going on for logstash-filter-verifier v 2.0. There we have some ideas to make this possible. See also: https://github.com/magnusbaeck/logstash-filter-verifier/issues/94#issuecomment-770877220

I solved this by returning the translation ID from the validation and then use the following helper function in the action like this: ```Go // Add validation error in the...

Hi @baywet Thanks for your detailed feedback. I can not go into all the details you mentioned due to lack of time, but I still want to share some of...