mirror of https://github.com/databricks/cli.git
eb76e5d3e8
This moves `git.FileSet` to `libs/fileset` and decouples it from the Git package. It is made aware of gitignore rules in parent directories up to the repository root as well as gitignore files in underlying directories through the `fileset.Ignorer` interface. The recursive directory walker is reimplemented with [filepath.WalkDir]. Follow up to #182. |
||
|---|---|---|
| .. | ||
| 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.