mirror of https://github.com/databricks/cli.git
bca9c2eda4
## Changes
We want to encourage a pattern of specifying only a single resource in a
YAML file when the `.(resource-type).yml` extension is used (for
example, `.job.yml`). This convention could allow us to bijectively map
a resource YAML file to its corresponding resource in the Databricks
workspace.
This PR:
1. Emits a recommendation diagnostic when we detect this convention is
being violated. We can promote this to a warning when we want to
encourage this pattern more strongly.
2. Visualises the recommendation diagnostics in the `bundle validate`
command.
**NOTE:** While this PR also shows the recommendation for `.yaml` files,
we do not encourage users to use this extension. We only support it here
since it's part of the YAML standard and some existing users might
already be using `.yaml`.
## Tests
Unit tests and manually. Here's what an example output looks like:
```
Recommendation: define a single job in a file with the .job.yml extension.
at resources.jobs.bar
resources.jobs.foo
in foo.job.yml:13:7
foo.job.yml:5:7
The following resources are defined or configured in this file:
- bar (job)
- foo (job)
```
---------
Co-authored-by: Lennart Kats (databricks) <lennart.kats@databricks.com>
|
||
|---|---|---|
| .. | ||
| generate | ||
| loader | ||
| mutator | ||
| resources | ||
| validate | ||
| variable | ||
| artifact.go | ||
| artifacts_test.go | ||
| bundle.go | ||
| deployment.go | ||
| experimental.go | ||
| filename.go | ||
| filename_test.go | ||
| git.go | ||
| lock.go | ||
| lock_test.go | ||
| presets.go | ||
| resources.go | ||
| resources_test.go | ||
| root.go | ||
| root_test.go | ||
| sync.go | ||
| target.go | ||
| workspace.go | ||
| workspace_test.go | ||