mirror of https://github.com/databricks/cli.git
18dae73505
This PR does multiple things, which are: 1. Creates .databricks dir according to outcomes concluded in "bricks configuration principles" 2. Puts the sync snapshots into a file whose names is tagged with md5(concat(host, remote-path)) 3. Saves both host and username in the bricks snapshot for debuggability Tested manually: https://user-images.githubusercontent.com/88374338/195672267-9dd90230-570f-49b7-847f-05a5a6fd8986.mov |
||
|---|---|---|
| .. | ||
| testdata | ||
| README.md | ||
| config.go | ||
| config_test.go | ||
| environment.go | ||
| environment_test.go | ||
| flavor.go | ||
| project.go | ||
| project_test.go | ||
| root.go | ||
| root_test.go | ||
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.