I discovered in #8 that it's necessary to add the postfix binaries to the PATH of the check_mk agent in order for the built-in postfix checks to work. I propose adding an option (extraPackages?) to the NixOS module allowing consumers to add things to the PATH without needed to explicitly know every systemd unit to which the things need to be added.
That seems uncontroversial, though if you have a better idea for the name of this option, I'd like to hear it.
It occurred to me that we could also add priority 100 (i.e. normal definition priority) statements like
services.check_mk_agent.extraPackages = lib.optional config.services.postfix.enable config.services.postfix.package;
to the module definition for common cases. (I don't know of any other examples off the top of my head.) Would you accept that, too, or would you prefer to not be in the business of maintaining a list of NixOS modules supported by this project?
I discovered in #8 that it's necessary to add the postfix binaries to the PATH of the check_mk agent in order for the built-in postfix checks to work. I propose adding an option (
extraPackages?) to the NixOS module allowing consumers to add things to the PATH without needed to explicitly know every systemd unit to which the things need to be added.That seems uncontroversial, though if you have a better idea for the name of this option, I'd like to hear it.
It occurred to me that we could also add priority 100 (i.e. normal definition priority) statements like
to the module definition for common cases. (I don't know of any other examples off the top of my head.) Would you accept that, too, or would you prefer to not be in the business of maintaining a list of NixOS modules supported by this project?