Importing den aspects in non-den configuration

[basbebe]

Say I have a nix config repo (a) making use of den aspects for defining hosts and users.

If I wanted to import some of these definitions as "traditional" nixosModules in another config repo (b) which doesn't use den:
How would I currently do that?

[theutz]

Take a look at the flake parts demo for inspiration, I think. Technically, you can resolve a set of aspects to any flake output, including nixosModules. Also, this section of the docs might be especially helpful.

[vic]

You can manually resolve an aspect into a module.

[basbebe]

Must have missed that the last time I looked into the docs, thanks.
Might try that route!

[mkapra]

The examples below are useful for debugging but should not be used in production configurations.

Is there a specific reason for this warning? Because the resulting modules would be used in production configurations in the end.

[vic]

the debugging guide tends to use internal apis, that's why there's that warning, but aspects.resolve was documented elsewhere as public api (iirc it is part of migration guides exactly for the purpose of this question)

[landure]

Hello,

I've had some success using den.lib.aspects.resolve to create a homeModule for each aspect.
Something like:

{
  den,
  inputs,
  ...
}:
let
  inherit (den.lib.aspects) resolve;

  aspectToHomeModule =
    name: aspect:
    { config, lib, ... }:
    let
      inherit resolve;
      inherit aspect;

      module = resolve "homeManager"  aspect;
    in
    {
      imports = [ module ];
    };

  aspectsToHomeModules =
    aspects: _:
    let
      inherit aspectToHomeModule;
    in
    {
      imports = builtins.attrValues (builtins.mapAttrs aspectToHomeModule aspects);
    };
in
{
  flake.homeModules = aspectsToHomeModules den.aspects;
}

This create an "unconditionnal" module for each aspect, that needs to be imported one by one in the consuming flake

My issue is with adding "conditional" imports based on an option named after the aspect. It create infinite recursion due to using config in imports.
I would like to have aspects like described in den, but flake modules being all imported at once, with standard config options to enable them.

Is there a way to prevent the infinite recursion ? I've tried playing with meta and functor without success.