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/acceptance/bundle/paths/nominal
History
Denis Bilenko 9320bd1682
acc: Use [VARNAME] instead of $VARNAME (#2282) 
$VARNAME is what we use for environment variables, it's good to
separate.

Some people use envsubst for homemade variable interpolation, it's also
good to have separation there.
 		2025-02-03 14:10:19 +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 acc: Use [VARNAME] instead of $VARNAME (#2282) 2025-02-03 14:10:19 +00:00
output.pipeline.json acc: Use [VARNAME] instead of $VARNAME (#2282) 2025-02-03 14:10:19 +00:00
output.txt acc: Use [VARNAME] instead of $VARNAME (#2282) 2025-02-03 14:10:19 +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).