Skip to content
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

Simplifying zabbix_agent requirements by separating it into it's own module? #774

Open
Wildcarde opened this issue Jun 22, 2021 · 0 comments
Labels

Comments

@Wildcarde
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 7
  • Distribution: centos 7/8, ubuntu (too many)

This is a question / suggestion more than an issue at this time. I'm working to integrate our puppetized machines into a pre-existing zabbix installation and have come to discover that the zabbix module has a rather considerable number of dependencies that all seem to be in service of the server and proxy sections of the code base rather than the agent side. Would it be considered reasonable to tease out the agent code into a smaller module that could be included directly and have the central zabbix module add that as an external dependency instead of requiring this entire gestalt module just add agents to a bunch of nodes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants