#short name + remote modules
1 messages ยท Page 1 of 1 (latest)
the most basic repro on my end. I must be doing something wrong?
dagger init
dagger install github.com/shykes/daggerverse/hello
dagger -m hello functions
aha can you try v0.9.10
I'm on 0.9.10 ๐
ah never mind ๐
am I getting the syntax wrong?
i don't ever remember adding support for this if i'm honest
that said, i might have missed this
maybe we collectively manifested it lol
Erik added it (or at least planned to)
@winter hatch did you have this working?
I've used this a lot lately but only with local paths. Should be supported so looks like we need a 0.9.11 ๐
Oh, wait, it created a dir structure with that path:
lt -a
.
โโโ github.com
โ โโโ shykes
โ โโโ daggerverse
โ โโโ hello@ac880927d5368eaf2e5d94450e587732753df1a6
โโโ dagger.json
Wrong reference format?
Woah... you're right... why did that happen
confirmed the shortname stuff works fine for local mods
This is ok:
dagger -m github.com/shykes/daggerverse/hello@ac880927d5368eaf2e5d94450e587732753df1a6 functions
So must be a bug.
opening issue to track it
today is the day of issues lol ๐
oh wait so is dagger install for remote modules bugged???
based on this I want to say yes?
oh it only happens when you try to reference the short name of the remote module, not on install
started an internal thread to discuss this ๐
What I expect to work: dagger init dagger install github.com/shykes/daggerverse/hello dagger -m hello functions What I get: Error: failed to get configured module: failed to get local root path: in...
@barren quiver is it actually voluntary to have that weird vendored directory in the module dir?
the github.com/<repo> directory? I don't think it's supposed to be there at all, I think that was a bug based on the code path assuming it was a local module vs remote
Right that's what I thought too. Different bug than the one you're fixing? Or it's one and the same?
It should be resolved as part of my fix, let me triple check
confirmed
super nice UX now
Next step is to let you install in your home directory if you're outside a module
So then dagger install always works
Yeah I like that. Still imagine the primary use case is a module definition at a project root so dagger "just works" almost like direnv
Related to this + the crawling discussion - would be kind of cool to have a versioned dagger-in-dagger for modules so that it works no matter what your installed cli is. The last chance to mess up compatibility between different dev's machines