#Calling a module from a private repo?

1 messages · Page 1 of 1 (latest)

clear kraken
#

How would I pass the -m flag to dagger call and pass it a private repo?

red atlas
#

Hey again @clear kraken party_gopher. Private modules are not yet supported but will be in the near future! This is a feature many folks have requested it as necessary so we definitely are planning for it.

In the meantime, if you have the opportunity to set everything up on a monorepo, you can refer to a module using a path. Lets say you have your repo with:

app1/module
app2/module
utils/module1
utils/module2

You can call any module from any location of the repository by telling -m the path to said module!

clear kraken
#

Damn. Our team over at Motion is explicitly not putting our dagger functions / modules in our monorepo for a few different reasons. This is going to be an immediate blocker for us to make any progress with Dagger. 😦

red atlas
#

The easiest workaround I can think of is to clone the repository of the module before calling in the context of the caller and referencing the path to it! Not sure what your setup looks like, but if you are using Gitlab CI then the runner will probably already have permissions to read repository contents! It's not ideal, but it's good enough for a PoC!

We will post updates for private module support on this issue: https://github.com/dagger/dagger/issues/6113

GitHub
✨ Zenith: Allow installing modules from private Git repositories. ·...

What are you trying to do? Currently you can only dagger mod install modules hosted in public Git repositories. While this is great for OSS, it's not ideal for Enterprises that use private Git ...