Calling dagger functions / modules from sdk | Dagger | Page 1

violet wyvern Feb 29, 2024, 11:13 AM

#

Hi all, I want to say dagger is an awesome tool.
I am trying to understand how to migrate to dagger 0.10 and make use of functions and modules. We basically have a python cli that parses a custom defined config file and then launches different dagger pipelines conditionally, based on settings and env vars (if it is CI or local). I am struggling to understand how we could achieve something similar and integrate dagger modules and functions in our CLI. Any thoughts?

flint verge Feb 29, 2024, 4:07 PM

#

hey there! that still hasn't been implemeneted yet, it's being tracked here: https://github.com/dagger/dagger/issues/5993

GitHub

Call a Zenith module from non-Zenith code · Issue #5993 · dagger/da...

Right now if you want to call 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 graphql queries for it. We ca...

opal trail Mar 2, 2024, 6:50 PM

#

@violet wyvern you have 2 options:

Option 1 is what @flint verge explained: modify your tool to call external functions, written either by you or the community. This is not yet supported.
Option 2: wrap your tool itself as a Dagger Function, and call it with dagger call. That works today.

Of course these are not mutually exclusive 🙂 You can start with option 2, and add option 1 later when it becomes possible .

#Calling dagger functions / modules from sdk