Hi all,
I have now finally some updates about the questions from the last call.
Regarding the overshadowing of shipped checks and rulesets, especially legacy ones:
As mentioned in the call, shipped plugins can be overridden by placing the modified plugins under ~/local/lib/python3/cmk/plugins instead of ~/local/lib/python3/cmk_addons/plugins.
API v2 check plugins take precedence over legacy checks and with #werk 18965 API v1 rulesets now also take precedence over legacy rulesets. The {family} folder is not important for the replacement of legacy plugins, only the name needs to match.
Regarding shipping additional python packages:
For bakery plugins this is not supported.
For normal plugins you can place the python package under ~/local/lib/python3, e.g. ~/local/lib/python3/paho. You can then package paho in your MKP and import from it as usual in your plugin.
Regarding the custom_validate field for MonitoredHost/MonitoredService:
Thanks to the question we noticed that the custom validation was not being triggered for a number of FormSpecs.
You can see the affected FormSpecs in #werk 18966.
Unfortunately this means invalid configurations may be present if you used the custom validation for any of the mentioned FormSpecs. Those will have to be fixed manually by the user when the validation now takes affect.