Hey guys! more or less following this

[gentle moon]

Hi Alex! Thanks for the detailed questions. I'll answer each in turn.

Is there any way to currently use the Dagger 'old fashion' way of creating pipelines importing 'zenith' modules?

Not yet, but it's planned, and will be available at release.

See https://github.com/dagger/dagger/issues/5993

what's the recommended approach when there's a main 'zenith' module —let's call it, a parent pipeline— and several child 'zenith' modules that live in different repositories?

I'm not 100% sure what you mean by "child module". Do you mean dependencies? If so, any module can call functions from another module by installing it as a dependency. Just run dagger mod install MODULE_NAME from the caller module.

I've seen that I can do a bit of exec.Command magic there, but it does not feel "pleasant" I'd say.

Could you walk me through what we're trying to achieve? I don't understand what this exec.Command scenario does exactly.

[austere wraith]

Hey @gentle moon , thanks as usual!
Oh! what a poor question I've made by including confusing terms 😢 , 'Child module' is indeed a zenith dependency. Nevertheless, you've also clarified this doubt too.

The exec.Command was an alternative to use plain shell commands emulating what the `dagger mod -m 'something' call does. However, since I'm able to reuse zenith modules into others, that won't be necessary.

What a great news is that it's going to be released soon! That fits very well to a lot of scenarios that I'm considering currently. By the way, and it's a bit out of topic; is it considered to support 'zenith' modules that can be registered into the daggerverse that are actually hosted in GitLab?

[gentle moon]

Yes we absolutely must support hosting Dagger Modules on Gitlab, or any other git hosting 👍

[smoky salmon]

Could you walk me through what we're trying to achieve? I don't understand what this exec.Command scenario does exactly

he's referencing the suggestion here: #daggernauts message