Dagger Python SDK: Develop Your CI/CD Pipelines as Code
1–10 of 92 posts
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#2Hi everyone, Dagger co-founder here. Happy to answer any questions.
We also released an update to the Go SDK a few days ago: https://dagger.io/blog/go-sdk-0.4
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#3Hey, lead developer for the Python SDK here.
I have a few examples in https://github.com/helderco/dagger-examples and I plan to add more.
There's also reference documentation in https://dagger-io.readthedocs.io/ so you can get a birds eye view on what's possible.
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#4Here's the demo video linked in the blog post: https://www.youtube.com/watch?v=c0bLWmi2B-4
It goes step by step through the getting started guide from the Dagger Python SDK docs
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#5Even if this was a great, well-built tool, which I am sure it is...
Doesn't this introduce a whole dimension of extra stateful complexity compared to configuration YAML?
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#6Haven't heard of Dagger before, but using IaC as code to model your pipelines (including pipelines of infra that itself is modeled as IaC) is absolutely the right way to do things. And doing it in a real programming language rather than some limiting yaml schema is so much nicer. Places I've worked at in the past would refer to these as meta pipelines or self-mutating pipelines.
For this reason, I love using the AWS CDK. Being able to model things in TypeScript was so much nicer than the janky flow of always feeling lost in some Ruby/JSON/YAML IaC template monstrosity.
Curious how Dagger differentiates itself from AWS CDK or cdktf.
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#7Hey, lead developer for the Python SDK here. I have a few examples in https://github.com/helderco/dagger-examples and I plan to add more. There's also reference documentation in https://dagger-io.readthedocs.io/ so you can get a birds eye view on what's possible.
Haven't tried it yet, but I like the features!
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#8While I prefer python over yaml, I tend to think imperative build systems are inherently more brittle.
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#9Even if this was a great, well-built tool, which I am sure it is... Doesn't this introduce a whole dimension of extra stateful complexity compared to configuration YAML?
But when we have control structures built on top of yaml (like ansible's `loop`, or `when`), we might as well just use proper programming language.
Re: Dagger Python SDK: Develop Your CI/CD Pipelines as Code
#10Haven't heard of Dagger before, but using IaC as code to model your pipelines (including pipelines of infra that itself is modeled as IaC) is absolutely the right way to do things. And doing it in a real programming language rather than some limiting yaml schema is so much nicer. Places I've worked at in the past would refer to these as meta pipelines or self-mutating pipelines. For this reason, I love using the AWS…
Dagger and IaC tools (AWS CDK, Terraform, Pulumi) are very complementary. Here's a livestream of Nic Jackson (devrel at Terraform) using Dagger and Terraform CDK together to build and deploy an application: https://www.youtube.com/watch?v=iFNe5W1o2_U
The main difference is that Dagger focuses on running your entire CI/CD pipeline as a DAG of operations running in containers; whereas IaC tools focus on managing infrastructure state. The typical integration is Dagger would run your IaC tool in a container, and integrate that into a broader pipeline with well-defined inputs and outputs. Dagger itself is stateless except for its cache: infrastructure state management is handed off to your IaC tool.