dan
/
liminix
1
0
Fork 5
Code Issues 3 Pull Requests 1 Projects Releases Wiki Activity
liminix/modules/service-trigger/rule.nix

25 lines
641 B
Nix
Raw Normal View History

wrap uevent-watch in a service
2024-06-02 17:27:59 +00:00
{
liminix
, uevent-watch
, serviceFns
, lib }:
{
flip dependencies for triggered/controlled services Instead of treating the trigger as the "main" service and the triggered service as subsidary, now we treat the triggered service as the service and the trigger as "subsidary". This needs some special handling when we work out which services go in the default bundle, but it works better for declaring dependencies on triggered services because it means the dependency runs after the triggered service comes up, not just when the watcher-for-events starts
2024-06-09 21:37:45 +00:00
serviceName, terms, symlink
wrap uevent-watch in a service
2024-06-02 17:27:59 +00:00
}:
let
inherit (liminix.services) longrun;
inherit (lib.attrsets) collect mapAttrsRecursive;
inherit (lib.strings) concatStringsSep;
stringify = attrs :
concatStringsSep " "
(collect lib.isString
(mapAttrsRecursive
(path : value : "${concatStringsSep "." path}=${value}")
attrs));
termsString = stringify terms;
in longrun {
flip dependencies for triggered/controlled services Instead of treating the trigger as the "main" service and the triggered service as subsidary, now we treat the triggered service as the service and the trigger as "subsidary". This needs some special handling when we work out which services go in the default bundle, but it works better for declaring dependencies on triggered services because it means the dependency runs after the triggered service comes up, not just when the watcher-for-events starts
2024-06-09 21:37:45 +00:00
name = "watch-for-${serviceName}";
wrap uevent-watch in a service
2024-06-02 17:27:59 +00:00
isTrigger = true;
flip dependencies for triggered/controlled services Instead of treating the trigger as the "main" service and the triggered service as subsidary, now we treat the triggered service as the service and the trigger as "subsidary". This needs some special handling when we work out which services go in the default bundle, but it works better for declaring dependencies on triggered services because it means the dependency runs after the triggered service comes up, not just when the watcher-for-events starts
2024-06-09 21:37:45 +00:00
run = "${uevent-watch}/bin/uevent-watch ${if symlink != null then "-n ${symlink}" else ""} -s ${serviceName} ${termsString}";
wrap uevent-watch in a service
2024-06-02 17:27:59 +00:00
}