-
-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gentoo service fix #545
Gentoo service fix #545
Conversation
Hey @lordievader , thank you for the PR. Accordingly to our reviewing policy new template are prefered with And you need to fix tests, some of them failed. |
The file |
So can you modify your PR to remove its use and fix tests ? |
@lordievader I'm aware :) But it's definitely not good style to just copy the file. This makes changes and maintenance way more complex. It could be enough to just add a parameter |
Oh, that does sound like a nicer fix. I'll implement that :) |
@lordievader can you rebase against our master and take a look at the failing spec tests? |
Since the Gentoo zabbix agent service is named different, it should be reflected in the userparameters.pp too.
In the previous Gentoo fixes I have to use the params.pp zabbix-agent service name it seems. Source service name from params.pp
@bastelfreak After quite a few attemps, I fixed the failing tests. As Gentoo doesn't seem part of the unit tests (I didn't see an easy way of adding the OS), I tested that part on my own system. |
Thanks! |
Pull Request (PR) description
This PR continues the Gentoo support of the puppet-zabbix module.
It fixes a few forgotten changes from
zabbix-agent
to$servicename
. Which is sourced fromparams.pp
.In the second commit a copy is made of
zabbix-agent-systemd.init.erb
and named aszabbix-agentd-systemd.init.erb
. I'm not sure if this is the wanted procedure, hence I left it as a separate commit. If this is not the correct procedure feel free to reject it ;)The last commit adds
$servicename
like support to userparameters.pp.