Hi all,

is there currently a possible workaround while we wait for this fix to be released?

@4levels: This has been merged more than a year ago already.

Hi @aszlig, this surprises me as I'm still running in exactly the same issue as described in the SO question here: https://stackoverflow.com/questions/50678639/how-to-change-the-serviceconfig-of-a-service-defined-in-nixpkgs-from-configurati

If I try to set the ExecStart part of the serviceConfig for eg. systemd.services.kibana I always get the following error: attribute 'systemd.services.kibana.serviceConfig.ExecStart' already defined without me explicitly defining it. If I adjust this to merge the existing kibana config, I get the infinite recursion error

I'm using the 19.03 channel..

I'm already setting a lot of systemd.services configurations myself, but not for kibana. I'll keep trying to find out if I can get it to work as expected. mkForce or mkOverride don't help either..

Did you try to override just the restart option, as suggested by OP?

{ systemd.services.nagios.serviceConfig.Restart = lib.mkForce "no"; }

Ok, I managed to get around it, like so:

systemd.services = mapAttrs' systemdService cfg.platforms
      // runners cfg.platforms // timers cfg.platforms
      // {
        kibana.serviceConfig.ExecStart = lib.mkForce (kibanaExecStart cfg.platforms);
      }

where the systemdService, runners, timers are custom sets of systemd serviceconfigs and cfg.platforms holds my service-setup.

So if I do it in one go, this works. If I try however to set the kibana serviceconfig afterwards, I'm stuck.

systemd.services = mapAttrs' systemdService cfg.platforms
      // runners cfg.platforms // timers cfg.platforms;
systemd.services.kibana.serviceConfig.ExecStart = lib.mkForce (kibanaExecStart cfg.platforms);

@4levels: Mhm, as @jtojnar mentioned, mkForce should work, here is a smaller PoC with 19.03 as you mentioned:

(import "${fetchTarball channel:nixos-19.03}/nixos" {
  configuration = { lib, ... }: {
    systemd.services.kibana.serviceConfig.ExecStart = lib.mkForce "foo";
  };
}).config.system.build.units."kibana.service"

Hi @aszlig, I guess it's because I'm already setting the systemd.services key to a set of my own serviceConfigs, which I seem to be able to do only once. If I omit the mkForce, I get the following error The unique option systemd.services.kibana.serviceConfig.ExecStart' is defined multiple times`. The whole setup I have here is obviously far more complex (nixops, overlays, legacy versions of packages, etc. etc.), but I'm very happy I still managed ;-)
Thanks for your quick responses!