steve/databricks-cli
steve
/
databricks-cli
mirror of https://github.com/databricks/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
databricks-cli/acceptance/bundle/templates/default-python/output/my_default_python
History
Denis Bilenko 2175dd24a4
Do not gitignore .databricks and terraform (#2318) 
For acceptance/bundle/templates I'd like to run "bundle deploy". This
would create .databricks directory inside materialized output. It might
makes sense to commit some of this as part of golden files output. Even
if we did not commit anything, the test runner will see those files and
show the difference. Thus git should also see them.

Also rename .gitignore to out.gitignore in those tests, since that
includes .databricks as well.
 		2025-02-10 11:42:39 +01:00
..
.vscode Include a materialized copy of built-in templates (#2146) 2025-01-17 15:03:59 +00:00
fixtures Include a materialized copy of built-in templates (#2146) 2025-01-17 15:03:59 +00:00
resources acc: Use [VARNAME] instead of $VARNAME (#2282) 2025-02-03 14:10:19 +00:00
scratch Switch to using `[` from `<` in text replacements (#2224) 2025-01-28 10:54:23 +00:00
src Switch to using `[` from `<` in text replacements (#2224) 2025-01-28 10:54:23 +00:00
tests Include a materialized copy of built-in templates (#2146) 2025-01-17 15:03:59 +00:00
README.md Include a materialized copy of built-in templates (#2146) 2025-01-17 15:03:59 +00:00
databricks.yml acc: Use [VARNAME] instead of $VARNAME (#2282) 2025-02-03 14:10:19 +00:00
out.gitignore Do not gitignore .databricks and terraform (#2318) 2025-02-10 11:42:39 +01:00
pytest.ini Include a materialized copy of built-in templates (#2146) 2025-01-17 15:03:59 +00:00
requirements-dev.txt Include a materialized copy of built-in templates (#2146) 2025-01-17 15:03:59 +00:00
setup.py acc: Use [VARNAME] instead of $VARNAME (#2282) 2025-02-03 14:10:19 +00:00

README.md

my_default_python

The 'my_default_python' 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] my_default_python_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/my_default_python.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

  6. Optionally, install developer tools such as the Databricks extension for Visual Studio Code from https://docs.databricks.com/dev-tools/vscode-ext.html. Or read the "getting started" documentation for Databricks Connect for instructions on running the included Python code from a different IDE.

  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.