Trying out a random idea: `dagger embed`

[past citrus]

If i'm able fine tune dagger like controlling log outputs etc, would be super amazing. Than I can use dagger as main executor and wrap functionality around it.

Trying out a random idea: dagger embed

[bold trellis]

I don't think I understand the benefits. If I'm embedding dagger in my own client, I'd just read the SDK documentation like I would do for any other project. Do you have another software in mind that does something similar? I'm guessing something like the cobra CLI allowing you to add commands? But I feel like that's super specific and it may get prohibitively difficult to account for a plethora of ways developers may embed Dagger in their clients.

It may be cool to do that but I feel like it's effort better spent elsewhere. I would prefer to use the existing dagger develop command to generate client bindings. Would be easier for me to remember one command instead of two.

[crimson timber]

using dagger develop to generate client bindings could work. But currently develop does more than that - so we would need a way to tell it to do the codegen part without the rest. And possibly the generated bindings might need to be written to a different location (not the module itself but the source of the host codebase? unless we have you drop the module where you want a go/python/typescript library to exist. Then codegen happens in place, and your dagger module becomes the library