Remove beat_install var

[levonet]

resolve #5

[levonet]

@Crazybus

[karlskewes]

Good find.
Just came up against this with deploying a change to filebeat.yml and the service not restarting.
There's a third reference to beat_install in both Debian and Rehat files, eg:

ansible-beats/tasks/beats-debian.yml

Line 11 in 74b3e8f

register: beat_install

I applied your patch plus removed the third reference above and the filebeat service was successfully restarted on config file change.

$ sudo journalctl -u filebeat | tail -n4
Jul 27 06:24:29 <hostname> systemd[1]: Started filebeat.
Aug 03 10:11:51 <hostname> systemd[1]: Stopping filebeat...
Aug 03 10:11:51 <hostname> systemd[1]: Stopped filebeat.
Aug 03 10:11:51 <hostname> systemd[1]: Started filebeat.
``

[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?

[Crazybus]

jenkins test this please

[levonet]

@Crazybus I tried to do this, but I have no idea how to check if service has been restarted.

[jmlrt]

jenkins test this please

[jmlrt]

LGTM 👍