Refresh service after package change (upgrade or downgrade)

[ghost]

This is to address issue reported at
#215.

We now refresh logstash service everytime there is a package change.
This is particulary useful when upgrading.

[elasticsearch-release]

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then say 'jenkins, test it'.

[ghost]

CLA was signed.

[elasticsearch-release]

Can one of the admins verify this patch?

[joshuaspence]

+1

[dutsmiller]

Is this going to be merged at some point. Without the change, upgrading is not fully automated.

[ninaspitfire]

I don't think so. This PR is a merge conflict now. It's not a great story, but it's a victim of the long period of low activity on this module. :(

What we really need is a new implementation, with acceptance coverage to prove that it works, and that it stays working.

[karmi]

Hi @VonFreud, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?