Expose `lib.helm.buildHelmChart` to downstream flakes

[kalbasit]

It's available in nixidy's lib under lib.helm.buildHelmChart: https://nixidy.dev/library/#libhelmbuildhelmchart

Sure, but that's only available to the modules I can't see a way to access that from the flake's inputs; From the flake, I can only access these libraries.

Originally posted by @kalbasit in #66 (comment)

[arnarg]

Sorry I misunderstood the original question. Doing this would be difficult as buildHelmChart needs an instance of pkgs so it would need to be under an attrset of different systems.

[srhb]

I'm unsure whether this helps @kalbasit, but:

I have a similar problem as the original post, and I'm wondering if it wouldn't suffice for many use cases to simply expose the result of helm.buildHelmChart ?

Right now applications/helm.nix encapsulates the logic a bit "too much" to get at the results directly, but if it round-tripped through some readonly attribute builtHelmChart (or whatever) in the config, we could simply fromCRD on that and applications/helm.nix could also the same result for the rest of the config.objects pipe. (readFile, fromYAML, transformer)

[kalbasit]

@arnarg yea it's not easy, I couldn't find a way to expose all of it as lib, how about mlib? Check out my proposed fix in #71. It's not elegant but it allows me to access it.

[kalbasit]

I'm unsure whether this helps @kalbasit, but:

I have a similar problem as the original post, and I'm wondering if it wouldn't suffice for many use cases to simply expose the result of helm.buildHelmChart ?

Right now applications/helm.nix encapsulates the logic a bit "too much" to get at the results directly, but if it round-tripped through some readonly attribute builtHelmChart (or whatever) in the config, we could simply fromCRD on that and applications/helm.nix could also the same result for the rest of the config.objects pipe. (readFile, fromYAML, transformer)

There are other use cases where it would be useful to access the library. For instance, I have my own chartsDir and I want to expose them the say way upstream nixHelm exposes them so I can pull the Helm chart locally. To that end I had to copy mkChartAttrs to my repo and I wish not to do that.

[arnarg]

Come to think of it, I could make a wrapper around fromCRD called fromChartCRD that looks something like this:

packages = {
  generators.cilium = nixidy.packages.${system}.generators.fromChartCRD {
    name = "cilium";

    chartAttrs = {
      repo = "https://helm.cilium.io/";
      chart = "cilium";
      version = "1.18.4";
      chartHash = "sha256-+8eiwQ5H5xy8S8/qHMYblGo8vc0IucrvfwLnWLWwrxU=";
    };
    # Or from nixhelm
    # chart = charts.cilium.cilium;

    crdFilter = [
      "CiliumNetworkPolicy"
      "CiliumClusterwideNetworkPolicy"
    ];
  };
};

This way, you don't need access to the lib functions. mkChartAttrs could be re-exported to output.packages.

[arnarg]

I've added the new function fromChartCRD: https://nixidy.dev/user_guide/typed_resources/#generating-resource-options-from-helm-chart-crds

[arnarg]

This has been worked around with the addition of fromChartCRD. Closing.