denik · Oct 9, 2026 · Oct 9, 2026 · Oct 9, 2026 · Oct 9, 2026 · Oct 9, 2026
@@ -0,0 +1 @@
+* Diagnostics about configuration values now consistently show the configuration path (`at ...`) and its location. ([#6999](https://github.com/databricks/cli/pull/6999))
@@ -19,6 +19,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:22:3
 
 Recreated internal_immutable_snapshots.immutable
@@ -42,6 +43,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:22:3
 
 The following resources will be deleted:

@@ -7,6 +7,7 @@
 
 >>> [CLI] bundle summary
 Warning: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:1:37
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.
@@ -26,6 +27,7 @@ Resources:
 
 >>> [CLI] bundle summary -o json
 Warning: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:1:37
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.

@@ -24,6 +24,7 @@ ID                   Type  Language  Path
 
 >>> [CLI] bundle run test_job --no-wait
 Warning: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:1:37
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.

@@ -1,6 +1,7 @@
 
 >>> musterr [CLI] bundle deployment migrate
 Error: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:3:11
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.

@@ -14,6 +14,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:5:3
 
 Notice: migrating your bundle to direct deployment engine (https://github.com/databricks/cli/issues/6765).
@@ -31,6 +32,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:5:3
 
 Success! Migrated 2 resources to direct engine state file: [TEST_TMP_DIR]/.databricks/bundle/production/resources.json
@@ -55,6 +57,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:5:3
 
 Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
@@ -70,6 +73,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:5:3
 
 
@@ -84,6 +88,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:5:3
 
 The following resources will be deleted:

@@ -1,4 +1,5 @@
 Error: target with 'mode: development' cannot set trigger pause status to UNPAUSED by default
+  at presets.trigger_pause_status
   in databricks.yml:9:29
 
 Name: preset

@@ -115,6 +115,7 @@ Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged
 === deleting the file warns and re-fires
 >>> [CLI] bundle plan -o json
 Warning: lifecycle.triggers.on_file_change: no synced files match "seed.txt"
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:18:29
 
 
@@ -168,6 +169,7 @@ Warning: lifecycle.triggers.on_file_change: no synced files match "seed.txt"
   }
 }
 Warning: lifecycle.triggers.on_file_change: no synced files match "seed.txt"
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:18:29
 
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/job-runs-on-file-change/default/files...
@@ -189,6 +191,7 @@ Resources: 1 created, 0 changed, 1 deleted, 1 unchanged
 
 >>> [CLI] bundle plan
 Warning: lifecycle.triggers.on_file_change: no synced files match "seed.txt"
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:18:29
 
 Plan: 0 to add, 0 to change, 0 to delete, 2 unchanged

@@ -2,6 +2,7 @@
 === a pattern that escapes the sync root is rejected
 >>> musterr [CLI] bundle validate
 Error: lifecycle.triggers.on_file_change: pattern "../shared/*.txt" is not under the sync root
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:24:29
 
 Name: job-runs-on-file-change-errors
@@ -15,6 +16,7 @@ Found 1 error
 === a glob that only matches directories warns
 >>> [CLI] bundle validate
 Warning: lifecycle.triggers.on_file_change: no synced files match "dirs/*"
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:24:29
 
 Name: job-runs-on-file-change-errors
@@ -28,6 +30,7 @@ Found 1 warning
 === a glob matching a directory and an excluded file warns
 >>> [CLI] bundle validate
 Warning: lifecycle.triggers.on_file_change: no synced files match "mixed/*"
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:24:29
 
 Name: job-runs-on-file-change-errors
@@ -41,6 +44,7 @@ Found 1 warning
 === a glob matching only excluded files warns
 >>> [CLI] bundle validate
 Warning: lifecycle.triggers.on_file_change: no synced files match "allexcluded/*"
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:24:29
 
 Name: job-runs-on-file-change-errors
@@ -54,6 +58,7 @@ Found 1 warning
 === a pattern that matches nothing warns
 >>> [CLI] bundle validate
 Warning: lifecycle.triggers.on_file_change: no synced files match "missing/*.txt"
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:24:29
 
 Name: job-runs-on-file-change-errors
@@ -67,6 +72,7 @@ Found 1 warning
 === ** is not supported
 >>> musterr [CLI] bundle validate
 Error: lifecycle.triggers.on_file_change: ** in "src/**" is not supported; use * for a single directory level
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:24:29
 
 Name: job-runs-on-file-change-errors
@@ -80,6 +86,7 @@ Found 1 error
 === an absolute pattern is rejected
 >>> musterr [CLI] bundle validate
 Error: lifecycle.triggers.on_file_change: pattern "/tmp/seed.txt" must be relative to the defining YAML file
+  at resources.job_runs.my_run.lifecycle.triggers[0].on_file_change
   in databricks.yml:18:29
 
 Name: job-runs-on-file-change-errors

@@ -10,6 +10,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:9:7
 
 {
@@ -56,6 +57,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:9:7
 
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/dev/files...

@@ -7,6 +7,7 @@ Warning: expected string, found sequence
 
 Error: Secret value must be a string
   at resources.secrets.secret1.value
+  in databricks.yml:7:7
 
 The secret value for "secret1" must be a string.
 

@@ -2,19 +2,23 @@
 >>> [CLI] bundle run foo
 Error: Script bar has no content
   at scripts.bar.content
+  in databricks.yml:7:14
 
 Error: Script foo has no content
   at scripts.foo.content
+  in databricks.yml:5:7
 
 
 Exit code: 1
 
 >>> [CLI] bundle run bar
 Error: Script bar has no content
   at scripts.bar.content
+  in databricks.yml:7:14
 
 Error: Script foo has no content
   at scripts.foo.content
+  in databricks.yml:5:7
 
 
 Exit code: 1
@@ -1,4 +1,5 @@
 Error: run_as section must specify exactly one non-empty identity: user_name, service_principal_name, or group_name
+  at run_as
   in databricks.yml:4:9
 
   "run_as": {},
@@ -1,4 +1,5 @@
 Error: run_as section must specify exactly one non-empty identity: user_name, service_principal_name, or group_name
+  at run_as
   in databricks.yml:5:3
 
 {

@@ -1,4 +1,5 @@
 Error: run_as section must specify exactly one non-empty identity: user_name, service_principal_name, or group_name
+  at run_as
   in databricks.yml:5:3
 
 {

@@ -1,4 +1,5 @@
 Error: run_as section must specify exactly one non-empty identity: user_name, service_principal_name, or group_name
+  at run_as
   in databricks.yml:5:3
 
 {

@@ -1,4 +1,5 @@
 Error: run_as section must specify exactly one non-empty identity: user_name, service_principal_name, or group_name
+  at run_as
   in databricks.yml:6:3
 
 Name: run_as

@@ -1,6 +1,7 @@
 
 >>> [CLI] bundle summary
 Warning: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:3:11
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.
@@ -19,6 +20,7 @@ Resources:
 
 >>> [CLI] bundle summary -o json
 Warning: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:3:11
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.
@@ -28,6 +30,7 @@ See https://docs.databricks.com/dev-tools/bundles/direct for details
 
 >>> musterr [CLI] bundle validate
 Error: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:3:11
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.
@@ -40,6 +43,7 @@ Found 1 error
 
 >>> musterr [CLI] bundle validate -o json
 Error: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:3:11
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.

@@ -44,6 +44,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:23:7
 
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/user_not_declared/files...
@@ -107,6 +108,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:47:7
 
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-bundle/shared_users_can_manage/files...

@@ -148,6 +148,7 @@ Warning: required field "name" is not set
   in databricks.yml:6:12
 
 Error: Missing app source code path or git source
+  at resources.apps.rname
   in databricks.yml:6:12
 
 app resource 'rname' should have either source_code_path or git_source field

@@ -185,6 +185,7 @@ Warning: required field "name" is not set
   in databricks.yml:7:7
 
 Error: Missing app source code path or git source
+  at resources.apps.rname
   in databricks.yml:7:7
 
 app resource 'rname' should have either source_code_path or git_source field

@@ -164,6 +164,7 @@ Warning: required field "name" is not set
   in databricks.yml:7:7
 
 Error: Missing app source code path or git source
+  at resources.apps.rname
   in databricks.yml:7:7
 
 app resource 'rname' should have either source_code_path or git_source field

@@ -10,6 +10,7 @@ Validation OK!
 
 >>> musterr [CLI] bundle validate -t terraform-target
 Error: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:10:15
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.
@@ -22,6 +23,7 @@ Found 1 error
 
 >>> musterr [CLI] bundle validate -t terraform-target
 Error: the Terraform deployment engine has been removed in Databricks CLI v1.20.0
+  at bundle.engine
   in databricks.yml:10:15
 
 Remove the "bundle.engine" setting (or set it to "direct") to deploy with the direct engine; existing Terraform state is migrated automatically. To keep using Terraform, revert to Databricks CLI v1.19.x.

@@ -1,6 +1,7 @@
 
 >>> [CLI] bundle validate
 Error: invalid value "invalid_engine" for bundle.engine (expected "direct")
+  at bundle.engine
   in databricks.yml:3:11
 
 Name: test-engine-config

@@ -1,6 +1,7 @@
 
 >>> [CLI] bundle validate
 Error: invalid value "invalid_engine" for bundle.engine (expected "direct")
+  at bundle.engine
   in databricks.yml:7:15
 
 Name: test-engine-config

@@ -10,6 +10,7 @@ Consider using a adding a top-level permissions section such as the following:
       level: CAN_MANAGE
 
 See https://docs.databricks.com/dev-tools/bundles/permissions.html to learn more about permission configuration.
+  at permissions
   in databricks.yml:5:3
 
 {

@@ -12,6 +12,7 @@ presets: # PRESETS
 
 >>> musterr [CLI] bundle validate -o json
 Error: prefix should contain the current username or ${workspace.current_user.short_name} to ensure uniqueness when using 'mode: development'
+  at presets.name_prefix
   in databricks.yml:25:16
 
 

@@ -2,9 +2,11 @@
 >>> [CLI] bundle validate
 Warning: invalid value "12" for enum field. Valid values are [READ WRITE MANAGE]
   at resources.secret_scopes.bad_levels.permissions[0].level
+  in databricks.yml:7:7
 
 Warning: invalid value "fuzz_badlevel" for enum field. Valid values are [READ WRITE MANAGE]
   at resources.secret_scopes.bad_levels.permissions[1].level
+  in databricks.yml:7:7
 
 Name: test-bundle
 Target: default
@@ -17,9 +19,11 @@ Found 2 warnings
 >>> [CLI] bundle validate --strict
 Warning: invalid value "12" for enum field. Valid values are [READ WRITE MANAGE]
   at resources.secret_scopes.bad_levels.permissions[0].level
+  in databricks.yml:7:7
 
 Warning: invalid value "fuzz_badlevel" for enum field. Valid values are [READ WRITE MANAGE]
   at resources.secret_scopes.bad_levels.permissions[1].level
+  in databricks.yml:7:7
 
 Name: test-bundle
 Target: default
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		* Diagnostics about configuration values now consistently show the configuration path (`at ...`) and its location. ([#6999](https://github.com/databricks/cli/pull/6999))