Skip to content

Conversation

@bjackman
Copy link
Contributor

@bjackman bjackman commented Nov 18, 2025

❯❯  git log -n 2
commit 2c0e70ee0c7d36902e6f2fd6d523dedfb5e51846 (HEAD -> firecracker-extraconfig, fork/firecracker-extraconfig)
Author: Brendan Jackman <[email protected]>
Date:   Mon Nov 10 15:20:49 2025 +0000

    fireracker: Add extraArgs option
    
    For experimentation, support adding arbitrary extra args.

commit b6c5f9c5008463f0769e4c6b70aa0a26c98c9fbb
Author: Brendan Jackman <[email protected]>
Date:   Fri Nov 7 13:42:11 2025 +0000

    firecracker: Add extraConfig option
    
    For experimentation with low-level settings, add support for merging in
    arbitrary options to the Firecracker config file, following the standard pattern
    in nixpkgs for this kind of thing.
    
    My immediate usecase for this is for experimenting with firecracker features
    that are not yet released, so it doesn't make sense to add more specific Nix
    options for those features.

For experimentation with low-level settings, add support for merging in
arbitrary options to the Firecracker config file, following the standard pattern
in nixpkgs for this kind of thing.

My immediate usecase for this is for experimenting with firecracker features
that are not yet released, so it doesn't make sense to add more specific Nix
options for those features.
For experimentation, support adding arbitrary extra args.
@bjackman bjackman changed the title Firecracker extraconfig extraConfig and extraArgs for firecracker Nov 18, 2025
};

firecracker.extraConfig = mkOption {
type = types.attrs;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That type does not merge. We need to use a submodule of attrs.

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

Successfully merging this pull request may close these issues.

2 participants