Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2025 10:01 AM
Create a single job that runs your migration notebook.
In the job settings, under Parameters, add a key like env with a default value (e.g., dev).
When you create different job runs (or schedule them), override the parameter:
For development runs, set env = dev.
For production runs, set env = prod.
env = dbutils.widgets.get("env")
source_db = "VP_DWH" if env == "prod" else "VD_DWH"
source_table_fqn = f"{source_db}.SALES.SALES_DETAIL"Yes, DABs are a great option if:
You want environment-specific configurations (dev, staging, prod) in a single deployment artifact.
You need CI/CD integration for Databricks Jobs.
With DABs:
Define job parameters per environment in bundle.yml:
environments:
dev:
jobs:
migrate-job:
parameters:
env: "dev"
prod:
jobs:
migrate-job migrate-job:
parameters:
env: "prod"