| 8 Apr 2025 |
 kalessin | Ok, so it's not just all of the imports phase? | 18:10:23 |
 Robert Hensing (roberth) |
But to really see the potential:
- Make significant cuts in modules-list.nix and fix a few broken options references
- Watch instantiation of toplevel go down from 4.0 to 1.4 seconds.
- https://github.com/NixOS/nixpkgs/issues/137168
Seems safe to assume the list hasn't shrunk in the past 3.5 years :)
| 18:18:07 |
| Robert Hensing (roberth) | I assumed vars generation would run on the host, being part of the config. Is this representative or accidentally wonky? https://github.com/Lassulus/vars/blob/066dbc738838b79be6bc80b88559cb88e0fffffd/testing.nix#L75 | 18:25:40 |
| Robert Hensing (roberth) | fwiw this way the test can't run on a darwin VM host, but that's probably besides the point | 18:27:50 |
| kalessin | It's one representation, e.g. in clan vars generation is done from on the developer machine, ahead of deploying to a nixos host. | 18:27:52 |
| kalessin | * It's one representation, e.g. in clan vars generation is done on the developer machine, ahead of deploying to a nixos host. | 18:28:43 |
| kalessin | Like the vars definitions get evaluated, the result is exported, something does the prompting, and interacts with some secrets backend, then that something uploads some result/generated vars to the nixos host, or a key to decrypt them (if the result/generated vars are uploaded through the nix store), to the nixos host, and finally when you get to nixos-rebuild switch on your nixos host, your secrets get "activated" by something else that matches how something laid out the result/generated vars. | 18:34:43 |
| kalessin | hope that helps 🥵 | 18:35:25 |
| kalessin | My effort here, is to figure out how the vars interfaces could be used in different systems: clan, nixops4, …, in order to help the vars PR progress, and figure out where things intersect and overlap, to see if some of the work can be shared across different systems. | 18:42:38 |
