Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config generator (nixos) #9

Closed
blaggacao opened this issue Apr 6, 2021 · 3 comments
Closed

config generator (nixos) #9

blaggacao opened this issue Apr 6, 2021 · 3 comments

Comments

@blaggacao
Copy link
Collaborator

blaggacao commented Apr 6, 2021

inputs.nixpkgs.lib.nixosSystem (genericConfigurationBuilder name value)

As stated here #7 (comment), we need an interface to be able to extend lib.nixosSystemwhile retatining the environment (pkgs, hostname, extraArgs, etc) from the genericConfigurationsBuilder.

It looks like

, nixosConfigurations ? { }

would not preserve the desired genericConfigurationsBuilder environment.

Provides ability to solve #7 downstream.

/cc @Pacman99

@blaggacao blaggacao mentioned this issue Apr 7, 2021
@blaggacao
Copy link
Collaborator Author

blaggacao commented Apr 7, 2021

Let extraModules be custom modules, then we need a full system evaluation with and without extraModules and compare them.

It does not seem like that is something to be achievable via pure module system.

@Pacman99
Copy link
Collaborator

Pacman99 commented Apr 7, 2021

Doing this within the module system would be very interesting. You would have to pass all modules as a specialArg - I think module arg would work for this too however. And then get access to nixosSystem within the module system. I'll try and play around with it and see if how it would work.

@blaggacao
Copy link
Collaborator Author

#17 implemented this in staging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants