#I feel like Dagger is expecting you
1 messages · Page 1 of 1 (latest)
Something else is wrong here, I have similar structure and it works fine. This feels like a permissions issue to me, is this repo private? If so, how are you giving the credentials to dagger?
You could be right, might be failing to access the modules from another repository under the same group, failing an then walking back up the paths to find something that works.
However, I did try the same thing locally with the same path and it produced the same error.
If I put .git at the end it doesn't have this problem.
I found a relevant note in the docs.
https://github.com/dagger/dagger/blob/188147594a8334299c4621cec694faf8f9f68440/docs/current_docs/api/remote-modules.mdx
The .git extension is optional for HTTP refs or explicit SSH refs, except for GitLab, when referencing modules stored on a private repo or private subgroup.
Thanks for finding that, I don't recall this .git (but also dont work with a ton of private repos) part, great to know!
cc @latent galleon @vivid basalt did we lose that part in the new docs? Can't find it here: https://docs.dagger.io/extending/remote-repositories/
looks like its here under the remote modules tab: https://docs.dagger.io/extending/remote-repositories/
Yup, it's still there