Question

A data engineering team manages a Databricks Asset Bundle that deploys a job to both a staging and a production workspace. When they promote a new release, they want the production job to always run the code from a specific, immutable Git tag rather than from files copied into the production workspace. Which approach best supports this requirement?

Accepted Answer

Configure the job task to use a Git source in databricks.yml, pinning it to the release tag, so the production deployment references the versioned Git commit directly.

Answer

Manually export the notebooks from staging and import them into the production workspace before each release.

Answer

Set bundle mode to 'development' for the production target so the workspace files are prefixed and isolated per release.

Answer

Store the code only in DBFS and reference the DBFS path in the job definition to guarantee immutability.