databricks-cli/project
Pieter Noordhuis 6258a1637d
Add environments to project configuration (#68)
2022-09-22 13:40:11 +02: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 Add environments to project configuration (#68) 2022-09-22 13:40:11 +02: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
flavor.go Comment out flavor.go (#60) 2022-09-15 09:46:11 +02:00
project.go Add environments to project configuration (#68) 2022-09-22 13:40:11 +02:00
project_test.go Add environments to project configuration (#68) 2022-09-22 13:40:11 +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.