What are Paradime YAML-Based Schedules?
Paradime YAML schedules are configuration-as-code definitions, allowing you to define, version, and manage your data pipeline schedules directly within your dbt project repository. The recommended layout is the.bolt/ folder — a directory at the root of your dbt project containing one or more YAML files, each declaring a set of schedules. This lets teams own their own files and avoid merge conflicts on a shared configuration.
The legacy single-file
paradime_schedules.yml at the project root is still fully supported. The two layouts can coexist, so you can adopt .bolt/ gradually..bolt/ folder for the folder layout’s discovery rules and examples.
Why Use YAML-Based Schedules?
- Version Control
- Schedule configurations are tracked alongside your dbt models
- Review schedule modifications through Pull Requests
- Enforce team review processes for schedule changes
- Infrastructure as Code
- Schedules are treated as code, not just UI configurations
- Easy replication across environments
- Enables automated deployment pipelines
- Team Collaboration
- Simplified schedule review process
- Standard formatting and validation
- Documentation lives with the code
How YAML-based schedules are deployed
Schedules are read from your repository’s default branch (usuallymain or master), or from a custom deployment branch if you set one.
- Automatic refresh: Paradime checks for changes every 10 minutes.
- Manual refresh: for immediate updates, open Bolt and click Parse Schedules.
Merge your changes to the deployment branch first — schedules only update from that branch.