-
-
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
Implement self.prefetch for zabbix_host #591
Implement self.prefetch for zabbix_host #591
Conversation
manifests/agent.pp
Outdated
@@ -223,6 +226,7 @@ | |||
$monitored_by_proxy = $zabbix::params::monitored_by_proxy, | |||
$agent_use_ip = $zabbix::params::agent_use_ip, | |||
$zbx_group = $zabbix::params::agent_zbx_group, | |||
$zbx_groups = $zabbix::params::agent_zbx_groups, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a datatype for the new option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done :)
@baurmatt can you take a look at the rubocop issues and add some tests for it? Thanks for the great work! |
f31598e
to
e40fbb3
Compare
@bastelfreak Thanks! :) I've fixed the rubocop issues. Will take a look at unit tests for the type/provider. |
This commits adds the following improvements to zabbix_host: * Implement self.prefetch (This allows the use of `puppet resource zabbix_host` as well as purging unmanaged zabbix_host resources) * Implement proper setters for all properties * Rename the `group` parameter to `groups` to allow multiple groups to be specified This is another change for voxpupuli#570.
@bastelfreak I've implemented all tests for the custom type. But the provider seems to be out of my league. From my understanding, that would require a complete mock of the Zabbix API. |
e40fbb3
to
a4750d4
Compare
Thanks for all the work! |
Hey, this commit broke our environments as the parameter group of manifests/resources/agent.pp was not renamed: |
@guzmanbraso First of all, sorry that it broke your environment! I will look into it and open up a new PR with the fix soon. |
Hey @guzmanbraso, so I've just tried to understand what the problem could be, but sadly failed. manifests/resources/agent.pp still has the puppet-zabbix/manifests/resources/agent.pp Lines 21 to 22 in 580b484
Could you please provide more information about what the problem is? |
@guzmanbraso Are you running To me, it looks like your puppetserver doesn't realise the |
@baurmatt, no need to be sorry, my message was not a complain, just wanted to share that information wiyh you guys. Because $groups was defined with spec I missed when fast searching for it and took as granted that $group had to be renamed. My bad @alexjfisher will check that out and get back to you, I did not tested if it was an environment isolation issue, thought it was something more basic but clearly it's not. I'll test that and get back to you. Thank you everyone for your support! |
There were similar errors reported when puppetlabs/apt gained a new parameter in one of its ruby types. See #569 (comment) |
I had exactly the same problem as @guzmanbraso |
I had exactly the same problem as @guzmanbraso Fixed after running Thanks @baurmatt and @alexjfisher for your support. |
Pull Request (PR) description
This commits adds the following improvements to zabbix_host:
puppet resource zabbix_host
as well as purging unmanaged zabbix_host resources)group
parameter togroups
to allow multiple groups tobe specified
This is another change for #570.
This Pull Request (PR) fixes the following issues