feat. request: system module

[stealingudc]

Title.

While a system module does indeed exist, I assume it's being wrapped in flake.nix to avoid the infinite recursion of pulling from kubix.result.
A workaround, that, albeit a bit ugly, works well for my projects:

# kubix.nix
{
  config,
  pkgs,
  lib,
  kubix,
  ...
}: let
  builtManifests = kubix.lib.buildManifests pkgs.system {inherit (config) manifests;};
in {
  imports = [
    # <path/to/some-manifest-declaration.nix>
  ];
  options.manifests = lib.mkOption {
    type = lib.types.attrs;
    default = {};
  };
  # ..do whatever with ${builtManifests}
}

# some-manifest-declaration.nix
{
  manifests.myManifest = {
    # declare your k8s manifest here
  };
}

The usefulness of being able to rebuild (and subsequently reapply) manifests at nixos-rebuild switch-time is... dubious at best, since k8s itself is so incredibly runtime-dependent, but it may be worth it in certain situations.

Really hope to see this implemented!

[skystar-p]

I am trying to understand your usecase, but I'm afraid I didn't get it well.
So my understanding is, you need some kind of nixos module which can be imported in your nixosConfigurations?

This is already able to do by importing kubix.nixosModules.kubix.

# your nixos configuration
  imports = [ kubix.nixosModules.kubix ];

  kubix.enable = true;
  kubix.manifests.test = {
    apiVersion = "v1";
    kind = "ConfigMap";
    metadata = {
      name = "example-configmap";
      namespace = "default";
    };
    data = {
      "example" = "data";
    };
  };

  environment.etc."example.yaml".source = "${config.kubix.result}/test.json";

then you can cat /etc/example.yaml to see that built manifest.

Is this can satisfy your usecase?