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 241562e2b1
Move git package to libs/git (#189) 
Fixes #185.
 		2023-01-31 19:19:16 +01:00
..
testdata Added creation of .gitignore for bricks project with cache dir path (#88) 2022-11-08 13:51:08 +01:00
README.md Added basic project configuration 2022-05-14 19:55:00 +02:00
config.go Run unit tests on windows and macos (#103) 2022-11-28 11:34:25 +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
flavor.go Comment out flavor.go (#60) 2022-09-15 09:46:11 +02:00
project.go Move git package to libs/git (#189) 2023-01-31 19:19:16 +01:00
project_test.go Reload .gitignore files if they have changed (#190) 2023-01-31 18:34:36 +01: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.