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 8cab9d92f3
`bricks deploy` MVP 		2022-10-31 12:09:52 +01:00
..
testdata Add environments to project configuration (#68) 2022-09-22 13:40:11 +02:00
README.md Added basic project configuration 2022-05-14 19:55:00 +02:00
config.go `bricks deploy` MVP 2022-10-31 12:09:52 +01:00
config_test.go Store project object in context.Context instead of global (#61) 2022-09-16 11:06:58 +02:00
environment.go Add environments to project configuration (#68) 2022-09-22 13:40:11 +02:00
environment_test.go Add environments to project configuration (#68) 2022-09-22 13:40:11 +02:00
project.go `bricks deploy` MVP 2022-10-31 12:09:52 +01:00
project_build.go `bricks deploy` MVP 2022-10-31 12:09:52 +01:00
project_install.go `bricks deploy` MVP 2022-10-31 12:09:52 +01:00
project_test.go Add environments to project configuration (#68) 2022-09-22 13:40:11 +02:00
root.go Reduce nesting (#72) 2022-09-22 15:03:30 +02:00
root_test.go Store project object in context.Context instead of global (#61) 2022-09-16 11:06:58 +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.