Skip to main content

Overview

During CI/CD processes, Paradime Turbo CI creates temporary schemas for testing. The schemas will be dropped automatically on Pull Request merged if: This macro identifies and drops these schemas on demand by identifying all schemas with prefix paradime_turbo_ci

Configure the drop_turbo_ci_schema macro

To clean up temporary schemas created during CI runs, you can create a custom macro in your dbt™️ project. Here’s how:
  1. Navigate to your dbt project’s macros folder
  2. Create a new file called drop_turbo_ci_schema.sql
  3. Add the following code to the file:
drop_turbo_ci_schema.sql
The above example is based on BigQuery, use DinoAI to adapt it to other Data Warehouse providers.

Usage

The drop_turbo_ci_schema macro helps clean up temporary schemas created during CI runs, with an optional dry-run mode for safe testing.

Arguments

  • dryrun (bool, optional)
    • True: Preview DROP commands without executing them
    • False: Execute DROP commands and remove schemas
    • Default: True (Safe mode)

Configure a Bolt Schedule

Set up a scheduled job in Paradime Bolt with the Below:

Schedule Settings

Command Settings

The template uses one commands that execute our macro and passes the argument dryrun set to false
  • dbt run-operation drop_turbo_ci_schema --args '{dryrun: false}' --target ci
Make sure to use the same --target used when running Paradime Turbo CI

Trigger Type

  • Type: Scheduled Run (Cron)
  • Cron Schedule: 0 8 * * 0 (Every Sunday at 8AM UTC)
For custom command configurations, see Command Settings documentation.

Notification Settings

  • Email Alerts:
    • Success: Confirms all schemas were dropped successfully, letting you know your data pipeline is healthy
    • Failure: Immediately alerts you when the macro fails to drops your Paradime Turbo Ci schema