Using Dagger modules from a custom VCS in a monorepo | Dagger | Page 1

I have many Dagger modules in a monorepo and a custom VCS. Git is also supported, but for obvious reasons the dagger -m <module> command takes an enormous amount of time.

Is there any way to use modules directly from a custom VCS at the moment (including proper versioning and everything that comes with it)?

One idea was to create a Dagger module that installs our VCS client and, inside that module, clones the repository and checks out the required version (for example, via a tag). But as far as I understand, the maximum I could return from such a module is just a directory with the module code. There is no way to make this “native”.

In other words, this would introduce CI/CD workarounds like:

clone module A
clone module B
clone module C
run module A
run module B
run module C

Moreover, it seems impossible to use one module as a dependency of another module in this setup.

Are there any viable options or recommended approaches here?

#Using Dagger modules from a custom VCS in a monorepo