databricks-cli/libs/template/templates/default-python/template/{{.project_name}}
Lennart Kats (databricks) f99716b0a5
Remove `run_as` from the built-in templates (#2044)
## Changes

This removes the `run-as` property from the default templates. It's a
useful property but it still only works for jobs and it makes the
default databricks.yml a bit longer. It seems like users can just learn
about it from the docs and/or vary their deployment identity.

Depends on https://github.com/databricks/cli/pull/1712.
2025-02-24 08:31:46 +00:00
..
.vscode Remove unused vscode settings in the templates (#2013) 2024-12-13 16:13:21 +00:00
fixtures Minor default template tweaks (#758) 2023-09-11 07:36:44 +00:00
resources Update target references to use `${bundle.target}` (#1935) 2024-11-27 11:51:08 +00:00
scratch Format default-python template (#2110) 2025-01-15 10:40:29 +01:00
src Format default-python template (#2110) 2025-01-15 10:40:29 +01:00
tests Fix DBConnect support in VS Code (#1253) 2024-03-05 14:31:27 +00:00
.gitignore Improve default template (#1046) 2023-12-11 19:13:14 +00:00
README.md.tmpl Provide instructions for testing in the default-python template (#2355) 2025-02-17 12:38:03 +00:00
databricks.yml.tmpl Remove `run_as` from the built-in templates (#2044) 2025-02-24 08:31:46 +00:00
pytest.ini databricks bundle init template v1 (#686) 2023-09-05 11:58:34 +00:00
requirements-dev.txt.tmpl Fix DBConnect support in VS Code (#1253) 2024-03-05 14:31:27 +00:00
setup.py.tmpl Format default-python template (#2110) 2025-01-15 10:40:29 +01:00

README.md.tmpl

# {{.project_name}}

The '{{.project_name}}' project was generated by using the default-python template.

## Getting started

1. Install the Databricks CLI from https://docs.databricks.com/dev-tools/cli/databricks-cli.html

2. Authenticate to your Databricks workspace, if you have not done so already:
    ```
    $ databricks configure
    ```

3. 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] {{.project_name}}_job` to your workspace.
    You can find that job by opening your workpace and clicking on **Workflows**.

4. Similarly, to deploy a production copy, type:
   ```
   $ databricks bundle deploy --target prod
   ```

   Note that the default job from the template has a schedule that runs every day
   (defined in resources/{{.project_name}}.job.yml). The schedule
   is paused when deploying in development mode (see
   https://docs.databricks.com/dev-tools/bundles/deployment-modes.html).

5. To run a job or pipeline, use the "run" command:
   ```
   $ databricks bundle run
   ```

{{- if (eq .include_python "no") }}
6. Optionally, install developer tools such as the Databricks extension for Visual Studio Code from
   https://docs.databricks.com/dev-tools/vscode-ext.html.
{{- else }}
6. Optionally, install the Databricks extension for Visual Studio code for local development from
   https://docs.databricks.com/dev-tools/vscode-ext.html. It can configure your
   virtual environment and setup Databricks Connect for running unit tests locally.
   When not using these tools, consult your development environment's documentation
   and/or the documentation for Databricks Connect for manually setting up your environment
   (https://docs.databricks.com/en/dev-tools/databricks-connect/python/index.html).
{{- end}}

7. 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.