Jane Jasperous:
Does this work for you?

colmena.my-host = { name, nodes, ... }:
{
   imports = [ self.nixosConfigurations.my-host ];
}; 

(if you get an error that deployment options are undefined, import colmena.nixosModules.deploymentOptions in your nixosConfiguration)

Fixes #48.

When too many lines of progress indication are being printed, scrollback will explode. It looks mostly fine if you're not scrolling back:

but if you make the terminal taller or scroll up, you'll see a problem:

This can drown out valuable output from the build phase or similar.

A simple way to reproduce this is to run colmena apply keys with the following hive.nix, in a terminal less than 20 lines tall:

with import <nixpkgs> {};
lib.genAttrs (map (n: "host${toString n}") (lib.range 1 20)) (name: {
  deployment.targetHost = "dummy.invalid";
  boot.isContainer = true;
  deployment.keys.block-deployment = {
    keyCommand = ["sleep" "infinity"];
  };
})

If for some reason the deployment target doesn't have an internet connection but does have binary caches enabled, copying the system closure will fail rather than falling back to copying directly.

In reply to @buckley310:matrix.org
because colmena was created before flakes were stable

In reply to @buckley310:matrix.org
So I'm curious. In my setup my servers all exist inside of my flake outputs.nixosConfigurations, and my outputs.colmena is just a stub that consumes nixosConfigurations and emits a colmena configuration. Is anyone else doing it this way, or just me? I really like the portability of keeping my hosts in nixosConfigurations

In reply to @schnecfk:ruhr-uni-bochum.de
Is there a specific reason for why colmena diverges from the "standard" flake output schema? (For reference: https://nixos.wiki/wiki/Flakes#Output_schema )