-
-
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
Add Zabbix 4.0 compatibility and new config_mode
parameter
#548
Conversation
@bastelfreak @dj-wasabi Any idea on the CI issue? The error is not explicit at all. |
Looks like the travis job had hung. I restarted it and all looks good now. |
The |
@alexjfisher Yeah not related but when I try to do my PR, I got a conflict because of that so I have to solve it by merging with the new values. |
It's best practice to use topic branches instead of making changes in your fork's master branch. Basically, your master branch should only ever contain changes that also exist in the upstream/master. If you are stuck with git issues, there are plenty of people who can help you out on both the IRC #voxpupuli channel or in the Puppet Community #voxpupuli slack channel. |
Could you rebase against our master branch and add zabbix 4 to our acceptance tests at https://github.com/voxpupuli/puppet-zabbix/tree/master/spec/acceptance ? |
Thanks @Lord-Y. Can you take a look at the used email address in your commits? It isn't associated with your github account. |
@bastelfreak Sorry, I'll make sure to better use git next time I'll commit, email, fork, rebase and else |
Hey, that's totally fine, nothing to worry about. You can always ping us in our IRC channel #voxpupuli on freenode or at https://puppetcommunity.slack.com if you've questions. It should be enough to add |
config_mode
parameter
Small updates to add Zabbix 4.0 compatibility