I would use the specialArgs parameter to pass datadir. You can use the same configuration if you use a let block and define it as variable or something.

In reply to @palo:xaos.space

I would use the specialArgs parameter to pass datadir. You can use the same configuration if you use a let block and define it as variable or something.

https://colmena.cli.rs/unstable/reference/meta.html#specialargs and https://github.com/nix-community/nixos-generators/blob/master/flake.nix#L29

In reply to @farcaller:matrix.org

In reply to @palo:xaos.space

I would use the specialArgs parameter to pass datadir. You can use the same configuration if you use a let block and define it as variable or something.

yeah, that's what I do in the generator config. I don’t think I can do the same with colmena, though

Yes you can :D

In reply to @yuka:yuka.dev
Probably lib.functionArgs is used on this function somewhere

In reply to @palo:xaos.space

https://colmena.cli.rs/unstable/reference/meta.html#specialargs and https://github.com/nix-community/nixos-generators/blob/master/flake.nix#L29

In reply to @ronnypfannschmidt:matrix.org
Are there any plans to support deployment of nixosSystem declarations in a flake?

A couple updates:

• More work was done on separating the evaluation logic from the deployment logic, with the new colmenaHive output being the integration point that ties the two halves together. Colmena can now deploy from the colmenaHive output which should be an already-evaluated hive generated by colmena.lib.makeHive (or your own logic!). Example here. cc David Arnold (blaggacao) Yureka (she/her)
• Flake-enabled deployments now use nix copy and the new SSH store protocol (ssh-ng://) for copying closures to remote hosts.

I'm getting the following error trying to use colmena to deploy to a remote host:

          | Failed: Child process exited with error code: 3
[ERROR] Failed to deploy to <remote host> - Last 9 lines of logs:
[ERROR]  created)
[ERROR]    state) Running
[ERROR]   stderr) activating the configuration...
[ERROR]   stdout) setting up /etc...
[ERROR]   stderr) reloading user units for root...
[ERROR]   stderr) setting up tmpfiles
[ERROR]   stderr) fchownat() of /blockchains/bitcoin failed: Invalid argument
[ERROR]  failure) Child process exited with error code: 3
[ERROR] Failed to complete requested operation - Last 1 lines of logs:
[ERROR]  failure) Child process exited with error code: 3
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 3

is there anything I do with colmena to get more debug output about exactly what is causing the failing fchownat line?

In reply to @rendakuenthusiast:imperishable.name

I'm getting the following error trying to use colmena to deploy to a remote host:

          | Failed: Child process exited with error code: 3
[ERROR] Failed to deploy to <remote host> - Last 9 lines of logs:
[ERROR]  created)
[ERROR]    state) Running
[ERROR]   stderr) activating the configuration...
[ERROR]   stdout) setting up /etc...
[ERROR]   stderr) reloading user units for root...
[ERROR]   stderr) setting up tmpfiles
[ERROR]   stderr) fchownat() of /blockchains/bitcoin failed: Invalid argument
[ERROR]  failure) Child process exited with error code: 3
[ERROR] Failed to complete requested operation - Last 1 lines of logs:
[ERROR]  failure) Child process exited with error code: 3
[ERROR] -----
[ERROR] Operation failed with error: Child process exited with error code: 3

is there anything I do with colmena to get more debug output about exactly what is causing the failing fchownat line?

I'm trying to not have to pass these into every single host.

        defaults = {
          imports = [
            inputs.agenix.nixosModules.age
            inputs.home-manager.nixosModules.home-manager
          ];
        };

I tried to add them to defaults and that works when deploying single host but if a deploy involves multiple ones then there is some kind of double inclusion error along the lines of:

error: The option `age.identityPaths' in `/tmp/.tmpPxgQXZ' is already declared in `/tmp/.tmpPxgQXZ'.

is there a more elegant way to avoid having to do reference these per-host?

In reply to @zhaofeng:zhaofeng.li

A couple updates:

• More work was done on separating the evaluation logic from the deployment logic, with the new colmenaHive output being the integration point that ties the two halves together. Colmena can now deploy from the colmenaHive output which should be an already-evaluated hive generated by colmena.lib.makeHive (or your own logic!). Example here. cc David Arnold (blaggacao) Yureka (she/her)
• Flake-enabled deployments now use nix copy and the new SSH store protocol (ssh-ng://) for copying closures to remote hosts.

Flake-enabled deployments now use nix copy and the new SSH store protocol (ssh-ng://) for copying closures to remote hosts.

Looks like this breaks buildOnTarget.

In reply to @winterqt:nixos.dev

Flake-enabled deployments now use nix copy and the new SSH store protocol (ssh-ng://) for copying closures to remote hosts.

Looks like this breaks buildOnTarget.