Reworking the processor implementation.

[corey-hammerton]

Instead of, what can become, a complicated original implementation migrating
filebeat processors to it's own defined type. There it's much easier to perform
some value checking before generating the configuration files in the config
dir location.

Orignally processors can only be declared using a class parameter like the following example

class{"filebeat": processors => [ { "drop_fields" => { "params" => {"fields" => ["input_type", "offset"]} } } ] }

Now they can be declared using defined type filebeat::processor, or still through $filebeat::processors but with a breaking format. Examples:

class{"filebeat": processors => { "my_processor" => { "processor_name" => "drop_fields", "params" => {"fields" => ["input_type", "offset"]} } } }

filebeat::processor{"my_processor": processor_name => "drop_fields", params => {"fields" => ["input_type", "offset"]} }

Have had issues with rake testing on my development environment which I cannot figure out. Travis CI testing may or may not be successful with the new test cases.

[corey-hammerton]

This provides a more reliable and permanent fix for #79

[pcfens]

I agree - I haven't had a chance to test this at all yet to be honest (everyone's been on vacation). I'm hoping to get it tested in the next few days and pushed up.

[corey-hammerton]

I'll fix the conflict on templates/filebeat5.yml.erb at my earliest convenience.

[pcfens]

I'm going to test this out and make sure I understand it (we don't use processors yet), and will hopefully merge this week to get it in for the next release. I put a note in the changelog that a breaking change will be showing up in the next feature release.

Thanks for taking the time on this.