Allow installing modules from private Git repositories.

[nipuna-perera]

What are you trying to do?

Currently you can only dagger install modules hosted in public Git repositories. While this is great for OSS, it's not ideal for Enterprises that use private Git repositories like Gitlab and Github Enterprise.

We require a way to somehow pass in/use authentication (GH PAT for example) when adding a module hosted in a private git repository.

Discord thread: https://discord.com/channels/707636530424053791/1171809848057401375

Why is this important to you?

• Companies in highly regulated industries cannot publish modules in the open. Git repositories hosted within our Github Enterprise instance requires authentication in order to access. This is a blocker for using dagger modules.
• Personal projects that don't want to create public Git repositories aren't currently supported.

How are you currently working around this?

No known workaround so far which makes this a high priority request for us and any others using private Git repositories to host Dagger modules.

[skycaptain]

Bringing attention back to this issue now that modules have become the default. (I suppose, as the docs only mention the modules and previous cookbooks and guides have been removed). For us, this is the only obstacle preventing us from using Dagger modules at present. I think this could be a Good First Issue. However, general approval on support this would be highly appreciated before beginning implementation.

[Alvise88]

If i want to add a private lib in go.mod the problem arise the same

[mehemken]

Just adding to the Why is this important to you? section.

I would like to keep my personal projects private.

No need to summon "highly regulated industry". It is just basic privacy.

[Transmitt0r]

Would be a very nice feature, I'm interested in using this with modules hosted on our internal Bitbucket instance.

[grouville]

This is under active development at this very moment

It is tightly linked to the implementation of #7218.

The first part is this PR: #7511, followed by another one for the directory refs, in which we unify the currently different way to reference directories and files on git remotes

This one has been unblocked recently by Erik's work on the CA certificates that allows passing SSH sockets securely. A draft PR shall be available this week, on which feedback from the community is welcome 😁