Andreas Rammhold

I am running into a similar issue. I have most of my machines follow the latest stable channel but some machines (currently just one) is following nixos-unstable due to changes...

Yeah, I went ahead and just apllied that patch to morph in my packages: https://github.com/andir/infra/blob/master/nix/packages/morph-evalConfig-machinename.patch I am still not entirely happy about that approach as now you have to specify...

A hacky(?) way to implement this would be: ```patch diff --git a/data/eval-machines.nix b/data/eval-machines.nix index 86ba52d..91332d0 100644 --- a/data/eval-machines.nix +++ b/data/eval-machines.nix @@ -7,6 +7,7 @@ let lib = network.network.lib or nwPkgs.lib...

Some part of the problem was that the `--post-build-hook` should/must recieve an absolute path to the hook that should be executed. That information is passed to the nix-daemon and there...

Just adding my 2cent here: I would love this feature but we must make sure to not "hide" deployment failures and not to short-circuit the deployments. I have a few...

Why not just use `nickel`? It is just three more characters.

> A quick update: after more discussion with @edolstra, we are focusing on Kubernetes, with a handful precise examples in mind that we will convert to Nickel, and then try...

> see also #84 Oh! I must have missed that when looking for "hooks" in the issue tracker :)

> Thanks for the suggestion. The request is not entirely new to us, but we've talked about experimenting with HTTP based hooks first, since the security implications are easier to...

> > Maybe we need to figure out how we can cut the morph deployments into more logical `phases` and then follow the intuition one gathers from `stdenv` where there...