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
Pieter Noordhuis a7701cc8f3
Store project object in context.Context instead of global (#61) 
* Load project root from `BRICKS_ROOT` environment variable
* Rename project.Project -> project.Config
* Rename project.inner -> project.project
* Upgrade cobra to 1.5.0 for cmd.SetContext
 		2022-09-16 11:06:58 +02:00
..
testdata Make tests pass (#40) 2022-09-07 20:08:42 +02:00
README.md Added basic project configuration 2022-05-14 19:55:00 +02:00
config.go Store project object in context.Context instead of global (#61) 2022-09-16 11:06:58 +02:00
config_test.go Store project object in context.Context instead of global (#61) 2022-09-16 11:06:58 +02:00
flavor.go Comment out flavor.go (#60) 2022-09-15 09:46:11 +02:00
project.go Store project object in context.Context instead of global (#61) 2022-09-16 11:06:58 +02:00
project_test.go Store project object in context.Context instead of global (#61) 2022-09-16 11:06:58 +02:00
root.go Store project object in context.Context instead of global (#61) 2022-09-16 11:06:58 +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.