calling out the modules from the SDK | Dagger | Page 1

cloud yarrow Jan 13, 2025, 9:25 PM

#

can you be more precise about what you're trying to do? x-SDK calls should work independent of language, they all end up going through the GQL, so it's unclear to me what sorta updates you're looking for

fervent plover Jan 13, 2025, 9:27 PM

#

SDK functions for loading/calling modules. Last I heard it wasn't supported, but Dagger was open to implementing it

#

Our top-level is not a module, we start with dagger run go run ./ci/main.go

ocean plume Jan 13, 2025, 9:45 PM

#

Hey @fervent plover, happy new year!

Sadly, no, this is still not possible.

@cloud yarrow just FYI this is a relatively common request, heres an issue tracking this one: https://github.com/dagger/dagger/issues/5993

GitHub

Call Dagger Functions from an external client · Issue #5993 · dagge...

Right now if you want to call functions available in a module, the only reasonable ways are from another module or from the CLI. Otherwise you are on your own to load the module and construct graph...

cold mason Jan 13, 2025, 10:42 PM

#

You can make the call itself, but you don't get generated client bindings for it. You need to make the raw http/graphql query yourself

#

For a simple integration (like a one-time function call to hand off to the module, and not too many complex arguments & return values to marshal & unmarshal, it could actually be all you need)

unborn python Jan 13, 2025, 10:53 PM

#

Here's an example on how to call a module from the SDK via GraphQL directly #1226443956213121105 message

#calling out the modules from the SDK