Think about assemble module for beats configuration

[widhalmt]

Since all beats share some parts of their configuration we could build them separately and use the assemble module to build the final version. That could reduce code redundancy.

[widhalmt]

@lbetz you were using assemble in another project. As you know, every beat has their own [beatname].yml configuration file where the second part is more or less identical.

Would you suggest to use assemble to build the files or would you say it's not worth the extra work? Could you think of a reason why people would want to have differing configuration for different beats, like logging?

[lbetz]

I would use Assemble if I wanted to determine and change the order of code snippets. But the order seems very static to me ...? I'd stick with one template here.