Bolt
With Bolt, you can efficiently deploy dbt™ in production. Instead of manually running commands, take advantage of Paradime's built-in scheduling to configure and automate the entire scheduling workflow.
Key Benifits
With Bolt, you can:
Maintain fresh production data on a consistent schedule
Execute CI/CD and production pipelines efficiently
Swiftly identify and resolve deployment issues
Utilize native integrations and custom webhooks for enhanced deployment
Scheduling Methods
Bolt offers two distinct approaches for managing dbt™ schedules in production:
UI-Based Schedules: Create and manage your dbt™ schedules through an intuitive user interface. All configurations available in YAML-based schedules are accessible here.
YAML-Based Schedules: Define and update your dbt™ schedules in the
paradime_schedules.yml
file within your Git repository, ideal for version-controlled configurations.
Bolt Terms
Understanding these key terms is crucial when configuring your schedules:
Term | Description | Example | Required |
---|---|---|---|
Type | Execution type for your scheduled dbt™ run | Standard, Deferred, or Turbo CI | Yes |
Name | Identifier for your dbt™ schedule | hourly_schedule | Yes |
Commands | dbt™ commands to execute (can be multiple) |
| Yes |
Git Branch | Branch used for schedule execution | main | Yes |
Owner Email | Schedule owner's email | me@email.com | Yes |
Trigger Type | How the schedule is initiated | Scheduled run, On Run Completion, On Merge, Cron Schedule | Yes |
Cron Schedule | Frequency of schedule runs (UTC-based) | @hourly | No |
Slack Notify On | When to send Slack notifications | failed and/or passed | No |
Slack Channels and Users | Recipients of Slack alerts | #data-team-alerts | No |
Email Notify On | When to send email notifications | failed and/or passed | No |
Email Notify | Email recipients for alerts | No |
Explore these topics for in-depth Bolt documentation, use cases, and tutorials:
Last updated