WIP: add Suse support for the monitoring_plugins role
AFAIK adding the Suse installation requires the community.general.zypper module (even though the task says ansible.builtin.package).
Should I add a collections/requirements.yml or a line in the galaxy.yml to make this visible?
And: Someone more experienced than me should maybe go over the list of available plugins. There are a lot more available. And I have not yet tested whether all that pointed to the tcp plugin in other vars files are also valid on Suse.
Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).
Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.
After that, please reply here with a comment and we'll verify.
Contributors that have not signed yet: @johanneskastl
-
If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.
-
If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.
Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).
Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.
After that, please reply here with a comment and we'll verify.
Contributors that have not signed yet: @johanneskastl
-
If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.
-
If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.
@cla-bot check
Should I add a collections/requirements.yml or a line in the galaxy.yml to make this visible?
Any opinions?