Question

A data engineering team uses Databricks Asset Bundles to deploy jobs. During development, jobs run under each developer's personal identity, which is fine for testing. However, when deploying to the production target, the team wants all jobs to run under a shared service principal rather than the identity of whoever last ran `databricks bundle deploy`. Which configuration approach in the bundle's databricks.yml achieves this for the production target?

Accepted Answer

Add a `run_as` setting with the service principal's `service_principal_name` under the production target's configuration.

Answer

Set the `DATABRICKS_TOKEN` environment variable to the service principal's personal access token before running deploy.

Answer

Add `git_source` referencing the service principal's repository under the production target.

Answer

Set `mode: production` on the target, which automatically makes all jobs run under the workspace owner.