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/project
History
Serge Smertin 95a68937fe rename `internal/test` to idiomatic `testdata` 2022-05-23 11:46:37 +02:00
..
testdata rename `internal/test` to idiomatic `testdata` 2022-05-23 11:46:37 +02:00
README.md Added basic project configuration 2022-05-14 19:55:00 +02:00
config.go added essential Python metadata detection 2022-05-20 21:40:03 +02:00
config_test.go rename `internal/test` to idiomatic `testdata` 2022-05-23 11:46:37 +02:00
flavor.go Add basic flavor skeleton 2022-05-14 20:56:02 +02:00
project.go local and remote `.tfstate` utilities 2022-05-21 15:23:37 +02:00

README.md

Project Configuration

Good implicit defaults is better than explicit complex configuration.

Regardless of current working directory, bricks finds project root with databricks.yml file up the directory tree. Technically, there might be couple of different Databricks Projects in the same Git repository, but the recommended scenario is to have just one databricks.yml in the root of Git repo.