50f62692ce
## Changes Include a materialized copy of built-in templates as reference output. This updates the output comparison logic to work against an output directory. The `doComparison` function now always works on real files. It can now tell apart non-existing files and empty files (e.g., the `.gitkeep` files in templates). |
||
---|---|---|
.. | ||
.vscode | ||
resources | ||
scratch | ||
src | ||
.gitignore | ||
README.md | ||
databricks.yml |
README.md
my_default_sql
The 'my_default_sql' project was generated by using the default-sql template.
Getting started
-
Install the Databricks CLI from https://docs.databricks.com/dev-tools/cli/install.html
-
Authenticate to your Databricks workspace (if you have not done so already):
$ databricks configure
-
To deploy a development copy of this project, type:
$ databricks bundle deploy --target dev
(Note that "dev" is the default target, so the
--target
parameter is optional here.)This deploys everything that's defined for this project. For example, the default template would deploy a job called
[dev yourname] my_default_sql_job
to your workspace. You can find that job by opening your workpace and clicking on Workflows. -
Similarly, to deploy a production copy, type:
$ databricks bundle deploy --target prod
-
To run a job, use the "run" command:
$ databricks bundle run
-
Optionally, install developer tools such as the Databricks extension for Visual Studio Code from https://docs.databricks.com/dev-tools/vscode-ext.html.
-
For documentation on the Databricks Asset Bundles format used for this project, and for CI/CD configuration, see https://docs.databricks.com/dev-tools/bundles/index.html.