logging: start Alloy after dynamic hostname setter when enabled

Signed-off-by: Everton de Matos <[email protected]>

Author: everton-dematos

modules/common/logging/client.nix

@@ -15,6 +15,7 @@ let
     ;
   cfg = config.ghaf.logging.client;
   inherit (config.ghaf.logging) listener;
+  dynHostEnabled = config.ghaf.identity.vmHostNameSetter.enable or false;
 in
 {
   options.ghaf.logging.client = {
@@ -125,7 +126,10 @@ in
     services.alloy.enable = true;
 
     systemd.services.alloy.serviceConfig = {
-      after = [ "systemd-journald.service" ];
+      after = [
+        "systemd-journald.service"
+      ]
+      ++ lib.optionals dynHostEnabled [ "set-dynamic-hostname.service" ];
       requires = [ "systemd-journald.service" ];
 
       # Once alloy.service in admin-vm stopped this service will

modules/common/logging/server.nix

@@ -16,6 +16,7 @@ let
     ;
   inherit (lib.strings) hasPrefix;
   cfg = config.ghaf.logging.server;
+  dynHostEnabled = config.ghaf.identity.vmHostNameSetter.enable or false;
 in
 {
   options.ghaf.logging.server = {
@@ -232,7 +233,10 @@ in
     services.alloy.enable = true;
 
     systemd.services.alloy.serviceConfig = {
-      after = [ "systemd-journald.service" ];
+      after = [
+        "systemd-journald.service"
+      ]
+      ++ lib.optionals dynHostEnabled [ "set-dynamic-hostname.service" ];
       requires = [ "systemd-journald.service" ];
 
       # If there is no internet connection , shutdown/reboot will take around 100sec