#If I wanted to get an early jump on
1 messages · Page 1 of 1 (latest)
With the obvious caveat that this isn't released and thus has an extra level of "no guarantees" in terms of stability, I've been generally keeping docs for writing Go extensions up to date here: https://github.com/dagger/dagger/blob/main/core/docs/y0yh0-writing_extensions_go.md
Go is probably the easiest to use so far because it's relatively low boilerplate and semi-documented. Python extensions are low boilerplate but highly experimental (and thus not documented yet). Nodejs extensions exist but we haven't yet reduced the boilerplate w/ code-first schemas yet, so you have to write graphql schema files by hand.
Another huge caveat you'll run into quickly is that we haven't integrate extensions w/ our codegen client SDKs yet, so the only way to invoke an extension right now is with raw graphql queries.
Great thanks! I will be taking a look at this. Long term will there be a "universe" of sorts for extensions?
My plan for now is to just to test these in my own repo, but long term it would be nice for there to be some sort of central collection
hmmm, I am running the latest version of dagger, but the dev sub command does not exist and the --sdk flag also does not exist. Is there a special version I need to install or is something needed to enable these new features?
ah looks like there are tags for version 3 going to try using those instead.
hmmm no luck, I did find the cloak executable which supports the needed commands though