databricks-cli/acceptance/bundle/paths/nominal
Pieter Noordhuis 89eb556318
Migrate path translation tests to acceptance tests (#2122)
## Changes

The assertions on the output made are now captured in the `output.*`
files. These don't capture intent like actual assertions do, but we
still have regular test coverage in the path translation tests under
`bundle/config/mutator`.

## Tests

Tests pass.
2025-01-17 10:22:49 +00:00
..
resources Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
src Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
README.md Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
databricks.yml Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
output.job.json Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
output.pipeline.json Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
output.txt Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
override_job.yml Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
override_pipeline.yml Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
script Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00
script.cleanup Migrate path translation tests to acceptance tests (#2122) 2025-01-17 10:22:49 +00:00

README.md

Test path translation (nominal behavior)

As of v0.216.0 (PR at https://github.com/databricks/cli/pull/1273), all paths in a resource definition are resolved relative to the directory of the file where they are defined.

This is more intuitive than the previous behavior (see ../fallback/README.md for details).