#What’s some really useful use cases for Dagger Go SDK that aren’t easily solved in other ways?

1 messages · Page 1 of 1 (latest)

terse ruin
#

Planning on trying out some dagger Go sdk magic.

Many of the use cases seem to involve Docker builds, which aren’t a particular problem area for me since I use goreleaser and mage.
I also don’t have a lot of dependency issues because go handles that so well.

I’d like to know are some great examples of go sdk development actions that Dagger has helped you with. with in a smoother way than before

untold frost
# terse ruin Planning on trying out some dagger Go sdk magic. Many of the use cases seem to...

👋 we've recently merged a PR that uses goreleaser within a Dagger pipeline (https://github.com/dagger/dagger/blob/main/internal/mage/cli.go#L21).

Some other use-cases that I find interesting:

goreleaser test still hasn't been implemented, so doing this in with the Dagger SDK would be neat (https://github.com/goreleaser/goreleaser/issues/2355).

If you check the main dagger mage targets here: https://github.com/dagger/dagger/blob/main/internal/mage/sdk/go.go you'll see that we have some steps like Lint Generate and Publish that are not supported currently in goreleaser.

There's also the possibility to copy embedded directories into a container (https://docs.dagger.io/110632/embed-directories). This could open the door for furhter use-cases with the SDK

#

Another topic is the the grpc / protobuf ecosystem. I've worked with grpc in the past and the tooling and pipeliens around it are not usually straightforward. I'd have loved to have a Go SDK library that helps me with all that back at that time when building docker images of this kind of apps