Hey everyone! 
New episode alert! 
Episode 55 is all about Terraform and the new Seqera Terraform Provider - bringing infrastructure-as-code to your Nextflow environments!
I’m joined by @kenibrewer and @Adam_Talbot to discuss why we built it, how it works, and why you might want to start using it.
The Problem:
We all love Nextflow’s “write once, run anywhere” philosophy - but what about the infrastructure underneath? If you’ve ever:
-
Clicked through the same Seqera Platform settings over and over
-
Wished you could version control your compute environment configs
-
Wanted to deploy identical workspaces across multiple teams
-
Needed audit trails for infrastructure changes in regulated environments
…then this episode (and the Terraform provider) is for you!
What We Cover:
-
Why infrastructure-as-code matters for bioinformatics
-
Ken’s journey from frustrated clicker to Terraform evangelist
-
How Terraform is like
nextflow -resumefor infrastructure -
The “cattle, not pets” philosophy for cloud resources
-
Real-world use cases: academic centers, clinical diagnostics, enterprise IT
-
Best practices and common pitfalls
-
How to get started (spoiler: AI is surprisingly good at writing Terraform!)
Key Takeaway:
What Nextflow did for pipelines, Terraform does for infrastructure. Declare your desired end state, let Terraform figure out the dependencies, and enjoy version-controlled, reproducible infrastructure with full audit trails.
Key resources:
-
Seqerakit - Python wrapper for Tower CLI
Show notes, transcript, links and more: https://seqera.io/podcasts/episode-55-terraform-seqera/
The episode is available now on YouTube, Spotify, and all other podcast platforms! 
As always, the podcast page has a detailed summary plus full transcript. Subtitles are manually curated!
Are you already using Terraform for your infrastructure? Thinking about trying the Seqera provider? Let us know below - the team is actively looking for feedback!
