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
shreyas-goenka 6bcb33bf07
Use env vars to read profile if databricks.yml is absent (#70) 
Tested manually and by running sync_test.go integration test bricks sync
works
 		2022-09-21 13:55:37 +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 Use env vars to read profile if databricks.yml is absent (#70) 2022-09-21 13:55:37 +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 Use env vars to read profile if databricks.yml is absent (#70) 2022-09-21 13:55:37 +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.