Skip to content

Mention bundle.engine in the doc #4786

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
denik merged 1 commit into from
Mar 18, 2026
Merged

Mention bundle.engine in the doc #4786

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/direct.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,12 @@ rm .databricks/bundle/my_target/resources.json

### Using on new bundles

For bundles that were never deployed, the migrate command will not work. Instead, deploy with an environment variable set: `DATABRICKS_BUNDLE_ENGINE=direct databricks bundle deploy -t my_target`.
For bundles that were never deployed, the migrate command will not work. To start using direct engine, you have two options:

- Set bundle.engine OR targets.\*.engine to "direct" in your databricks.yml
- Set DATABRICKS_BUNDLE_ENGINE=direct env var before the deployment.

If both are provided, the config takes precedence over the env var.

## Differences from terraform

Expand Down
Loading