imports = value._module.args.modules; seems promising, but as I add colmena.nixosModules.deploymentOptions to the nixosSystem modules, I now get a duplicate definition warning:

error: The option `deployment.allowLocalDeployment' in `<unknown-file>' is already declared in `/nix/store/4ba8vi60ay3b68kgspyxd7bmxbsixar1-source/flake.nix'.

and for reference, this is how i use it.

let
      hosts = import ./hosts hardware self.nixosModule;
      deploy = sconfig.lib.deploy { inherit self hosts; };
in
{
      inherit (deploy) colmena;
      nixosConfigurations = builtins.mapAttrs (_: nixpkgs.lib.nixosSystem) hosts;
}

./hosts looks like

hardware: nixosModule:
with hardware;

let
  sys = system: mods: {
    inherit system;
    modules = [ nixosModule ] ++ mods;
  };

in
{
   host1 = sys "x86_64-linux" [ ./host1 ];
}

./hosts/default.nix looks like

hardware: nixosModule:
with hardware;

let
  sys = system: mods: {
    inherit system;
    modules = [ nixosModule ] ++ mods;
  };

in
{
   host1 = sys "x86_64-linux" [ ./host1 ];
}

In reply to @buckley310:matrix.org
i had played with that strategy before, so i had it ready, just wasnt using it. basically instead of colmena consuming nixosConfigurations, just build my hosts as plain configs, and both nixosConfigurations and colmena consume that

hey team i'm hoping someone can help me out here...
i'm attempting to create a colmena managed nixos server using flakes
warning this is my first attempt at using flakes 😄

here is my flake.nix:

{
  description = "test";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs";
  };

  outputs = { self, nixpkgs }: {
    colmena = {
      meta = {
        nixpkgs = import nixpkgs {
          system = "x86_64-linux";
        };
      };

      hetzner-test-01 = {
        imports = [
          ./hardware/hetzner-test-01.nix
        ];
      };
    };
  };
}

i'm running into a mountain of errors when i run colmena build

here is a snippet:

[ERROR] Cacheable portion of option doc build failed.
[ERROR] Usually this means that an option attribute that ends up in documentation (eg `default` or `description`) depends on the restricted module arguments `config` or `pkgs`.
[ERROR] 
[ERROR] Rebuild your configuration with `--show-trace` to find the offending location. Remove the references to restricted arguments (eg by escaping their antiquotations or adding a `defaultText`) or disable the sandboxed build for the failing module by setting `meta.buildDocsInSandbox = false`.

for reference hardware/hetzner-test-01.nix is pretty simple:

{ modulesPath, ... }: {
  # imports = [ (modulesPath + "/profiles/qemu-guest.nix") ];

  boot.loader.grub.device = "/dev/sda";
  boot.initrd.kernelModules = [ "nvme" ];
  fileSystems."/" = {
    device = "/dev/sda1";
    fsType = "ext4";
  };
}

In reply to @aanderse:nixos.dev

here is a snippet:

[ERROR] Cacheable portion of option doc build failed.
[ERROR] Usually this means that an option attribute that ends up in documentation (eg `default` or `description`) depends on the restricted module arguments `config` or `pkgs`.
[ERROR] 
[ERROR] Rebuild your configuration with `--show-trace` to find the offending location. Remove the references to restricted arguments (eg by escaping their antiquotations or adding a `defaultText`) or disable the sandboxed build for the failing module by setting `meta.buildDocsInSandbox = false`.