beat config improvements

[MartinVerges]

In order to offer additional configuration possibilities which we use internally, I have extended the template accordingly by the variable bead_additional_conf. So it is possible to create any beat configuration.

Furthermore our lint test showed some bugs which will be fixed with the second commit.

I would be happy about a merge!

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[cla-checker-service]

Author of the following commits did not sign a Contributor Agreement:
0ae347b, 5c8efb6

Please, read and sign the above mentioned agreement if you want to contribute to this project

[cla-checker-service]

Author of the following commits did not sign a Contributor Agreement:
0ae347b, 5c8efb6, 07534e4

Please, read and sign the above mentioned agreement if you want to contribute to this project

[jmlrt]

Hi @MartinVerges,
Any beat configuration can be added via {{ beat_conf }} ansible variable.
Can you provide an example where it would make sense to use {{ beat_additional_conf }} variable instead of {{ beat_conf }}?

[MartinVerges]

hi, for example to configure filebeat.modules or setup.kibana or any of all the other options within the reference configuration of the beats.

[jmlrt]

You can already configure filebeat.modules, setup.kibana or any configuration mentioned in filebeat-reference-yml via beat_conf variable.

[MartinVerges]

hmm ok, good to know ;)
then the rest of the changes are just fixes for ansible-lint and yamllint.

[jmlrt]

⛴

[jmlrt]

jenkins test this please