🗓️Workflow as Code
Also known as Pipelines as Code, Workflows as Code, Orchestration as Code
Writing the steps of a pipeline in a code file. No clicks in a tool.
Think of it like
It is like a recipe written down, not kept in the cook's head. Anyone can read it, copy it and fix it.
Example
Emma's team keeps every pipeline as a Python file in git. A change to the sales pipeline goes through review first. When a run breaks, git shows what changed and who changed it.
Why it matters
Clicked-together pipelines are hard to review, copy or undo. Code can be read, tested and rolled back.
Definition
Common mistake
Key takeaways
- 1One file. Steps and order are written down.
- 2In version control. Every change has a history.
- 3Reviewed and tested. Like any other program.