3 ms·
Ending Support for the Dagger Cue SDK
- verdverm 3y agoLong time coming, I helped them build the early versions of this It is really hard to marry the BuiltKit evaluator with CUE's evaluator. They both are doing similar things, but for a different outcome. That being said, I think you could wrap Dagger's Go SDK in CUE and avoid the issue by not having such tight integration, but rather a sort of transpiler from CUE -> Go SDK. Something I told them I'd work on but haven't gotten to. The new GraphQL interface would make CUE even hard to use as a direct integration (recursion is very limited in CUE, while the Dagger GraphQL reminds you of the days of JS async pyramids) All this being said, I generally like writing build steps and logic in a general purpose language, and this is how I use Dagger. Probably also the reason I haven't been motivated to work on a CUE Dagger integration, it's painful to write ordered statements in a reusable/composable way.