#Is there a way to install `dagger-cue` from source?

1 messages · Page 1 of 1 (latest)

wise warren
#

I have https://github.com/dagger/dagger checked out but installing cmd/dagger seems to only works for Go sdk ?

I have also read https://docs.dagger.io/sdk/cue/526369/install but no mention of how to do that over there.

I tried specifying "sdk": "cue" in dagger.json file but that just gives me the Error: failed to solve: unknown sdk "cue" error.

GitHub

A programmable CI/CD engine that runs your pipelines in containers - GitHub - dagger/dagger: A programmable CI/CD engine that runs your pipelines in containers

{@include: ../../../partials/_install-sdk-cue.md}

#

And.... I figured it out right after I posted the quesion facepalm

I guess I'll leave it here in case someone else is looking for the same solution:

So I was looking at:
https://github.com/dagger/dagger/tree/cue-sdk

And so you need to:

  1. Checkout the cue-sdk branch
  2. Run go install -v ./cmd/dagger as usual
lucid parrot
#

Hi @wise warren ! Sorry about that, the CUE SDK is kind of a special case, since it existed before any other.

wise warren
#

Yeah realized that @lucid parrot , thanks!

lucid parrot
#

We plan on moving that code into main like the rest. This branch is a temporary transition stage

wise warren
#

Eventually this'll be configured in dagger.json right?

lucid parrot
#

Right, the current CUE SDK is based on the older Dagger Engine 0.2, whereas Go SDK is based on 0.3.

Once CUE SDK is ported to 0.3 (work in progress, no ETA yert), the "guts" will all be the same. Same CLI, same config files etc

#

Note that dagger.json itself is kind of a "hidden" feature at the moment, not guaranteed to be stable

#

Same for the dagger CLI in the dagger/dagger repo, which actually should not even be there.. Officially there is dagger CLI 0.3 yet, we plan on releasing it in 2 weeks or so

#

Complicated I know... again it's all because of the transition from 1 to 2 SDKs. Soon the dust will settle and it will all be much simpler 🤞