databricks · misha-db · Mar 16, 2026 · Mar 13, 2026 · Mar 14, 2026 · Mar 14, 2026
diff --git a/packages/databricks-vscode/CHANGELOG.md b/packages/databricks-vscode/CHANGELOG.md
@@ -349,7 +349,7 @@
 
 -   Feature: Add a interface for specifying bundle variables.
 -   Feature: Allow opting out of cluster override and make it more visible in UI.
--   Feature: Update databricks CLI to v0.218.0. Databricks Asset Bundles (DABs) are now GA!
+-   Feature: Update databricks CLI to v0.218.0. Declarative Automation Bundles (DABs) are now GA!
 -   Feature: Add UI and wizard to help manage virtual environments and Databricks Connect v2 versions.
 
 # Release: v2.0.4-preview
@@ -387,7 +387,7 @@
 
 ## <small>v2.0.1-preview (2024-03-07)</small>
 
--   Databricks Asset Bundles (DABs) are now available in VS Code which allows you to:
+-   Declarative Automation Bundles (DABs) are now available in VS Code which allows you to:
     -   easily set up, author and run Databricks projects from VS Code.
     -   leverage the DABs Resource Explorer so you can easily see all your Jobs and Pipelines in one place and run them with one click.
 -   All our run methods are now consolidated into 1 run menu.

diff --git a/packages/databricks-vscode/DATABRICKS.quickstart.md b/packages/databricks-vscode/DATABRICKS.quickstart.md
@@ -6,7 +6,7 @@ The Databricks extension for Visual Studio Code enables you to connect to your r
 
 # Features
 
--   Define, deploy, and run Databricks Asset Bundles to apply CI/CD patterns to your Databricks jobs, Delta Live Tables pipelines, and MLOps Stacks.
+-   Define, deploy, and run Declarative Automation Bundles to apply CI/CD patterns to your Databricks jobs, Delta Live Tables pipelines, and MLOps Stacks.
 -   Run local Python code files on Databricks clusters.
 -   Run notebooks and local Python code files as Databricks jobs.
 -   Set up and configure your debugging environment and Databricks Connect using a simple checklist that triggers selection dialogs.
@@ -21,9 +21,9 @@ The Databricks extension for Visual Studio Code enables you to connect to your r
         -   [Running Python files](#running-pyspark-code)
         -   [Running Notebooks as Workflows](#running-code-as-workflows)
         -   [Debugging and running Notebooks cell-by-cell using Databricks Connect](#running-notebook)
-    -   [Deploying Databricks Asset Bundles](#dabs)
-        -   [What are Databricks Asset Bundles?](#what-is-dab)
-        -   [Deploying Databricks Asset Bundles](#deploy-dab)
+    -   [Deploying Declarative Automation Bundles](#dabs)
+        -   [What are Declarative Automation Bundles?](#what-is-dab)
+        -   [Deploying Declarative Automation Bundles](#deploy-dab)
         -   [Run a Job or Pipeline](#deploy-run-job-pipeline)
 -   [Changes from v1](#changes-from-v1)
     -   [Migrate a project from Databricks extension v1 to v2](#migrate-from-v1)
@@ -46,7 +46,7 @@ The Databricks extension for Visual Studio Code enables you to connect to your r
 
 ![create-databricks-project](./images/dabs_vsc.gif)
 
-If your folder has multiple [Databricks Asset Bundles](#dabs), you can select which one to use by clicking "Open Existing Databricks project" button and selecting the desired project.
+If your folder has multiple [Declarative Automation Bundles](#dabs), you can select which one to use by clicking "Open Existing Databricks project" button and selecting the desired project.
 
 ## <a id="select-cluster"></a>Select a cluster
 
@@ -84,13 +84,13 @@ This will run the file using the Jobs API on the configured cluster and render t
 
 The extension provides easy setup for cell-by-cell running and debugging notebooks locally using Databricks Connect. For more details on how to set up Databricks Connect, refer to the [full docs](https://docs.databricks.com/en/dev-tools/vscode-ext/notebooks.html).
 
-## <a id="dabs"></a>Deploying Databricks Asset Bundles
+## <a id="dabs"></a>Deploying Declarative Automation Bundles
 
-### <a id="what-is-dab"></a>What are Databricks Asset Bundles?
+### <a id="what-is-dab"></a>What are Declarative Automation Bundles?
 
-Databricks Asset Bundles make it possible to describe Databricks resources such as jobs, pipelines, and notebooks as source files. These source files provide an end-to-end definition of a project, including how it should be structured, tested, and deployed, which makes it easier to collaborate on projects during active development. For more information, see [Databricks Asset Bundles](https://docs.databricks.com/en/dev-tools/bundles/index.html).
+Declarative Automation Bundles make it possible to describe Databricks resources such as jobs, pipelines, and notebooks as source files. These source files provide an end-to-end definition of a project, including how it should be structured, tested, and deployed, which makes it easier to collaborate on projects during active development. For more information, see [Declarative Automation Bundles](https://docs.databricks.com/en/dev-tools/bundles/index.html).
 
-### <a id="deploy-dab"></a>Deploying Databricks Asset Bundles?
+### <a id="deploy-dab"></a>Deploying Declarative Automation Bundles?
 
 1. In the Databricks extension panel, find the "Bundle Resource Explorer" view.
 2. Click on the "Deploy" button.
@@ -100,7 +100,7 @@ Databricks Asset Bundles make it possible to describe Databricks resources such
 
 ### <a id="deploy-run-job-pipeline"></a>Run a Job or Pipeline
 
-You can run a job or a pipeline managed by Databricks Asset Bundles, from the "Bundle Resource Explorer" view.
+You can run a job or a pipeline managed by Declarative Automation Bundles, from the "Bundle Resource Explorer" view.
 
 1. In the Databricks extension panel, find the "Bundle Resource Explorer" view.
 2. Hover over the job or pipeline that you want to run.
@@ -121,7 +121,7 @@ By default, a job is run using a jobs cluster. You can change this behavior and
 
 ## <a id="migrate-from-v1"></a>Migrate a project from Databricks extension v1 to v2
 
-If you are using Databricks extension v1, your project will automatically be migrated a [Databricks Asset Bundle](#what-is-dab) when you open it in v2. The migration process will create a new [`databricks.yml`](#what-is-databricksyml) file in the root of your project and move the configurations from the old `.databricks/project.json` to the new `databricks.yml` file.
+If you are using Databricks extension v1, your project will automatically be migrated a [Declarative Automation Bundle](#what-is-dab) when you open it in v2. The migration process will create a new [`databricks.yml`](#what-is-databricksyml) file in the root of your project and move the configurations from the old `.databricks/project.json` to the new `databricks.yml` file.
 
 > **Note**: This means that you will start seeing a `databricks.yml` file in your project root directory and in your version control system change logs. We recommend comitting this file to your version control system.
 

diff --git a/packages/databricks-vscode/README.md b/packages/databricks-vscode/README.md
@@ -6,7 +6,7 @@ The extension is available from the [Visual Studio Marketplace](https://marketpl
 
 ## Features
 
--   Define, deploy, and run Databricks Asset Bundles to apply CI/CD patterns to your Databricks jobs, Delta Live Tables pipelines, and MLOps Stacks.
+-   Define, deploy, and run Declarative Automation Bundles to apply CI/CD patterns to your Databricks jobs, Delta Live Tables pipelines, and MLOps Stacks.
 -   Run local Python code files on Databricks clusters.
 -   Run notebooks and local Python code files as Databricks jobs.
 -   Set up and configure your debugging environment and Databricks Connect.

diff --git a/packages/databricks-vscode/package.json b/packages/databricks-vscode/package.json
@@ -206,7 +206,7 @@
             {
                 "command": "databricks.connection.bundle.selectTarget",
                 "icon": "$(gear)",
-                "title": "Select a Databricks Asset Bundle target",
+                "title": "Select a Declarative Automation Bundle target",
                 "enablement": "databricks.context.activated",
                 "category": "Databricks"
             },

diff --git a/packages/databricks-vscode/resources/migration-template/template/databricks.yml.tmpl b/packages/databricks-vscode/resources/migration-template/template/databricks.yml.tmpl
@@ -1,4 +1,4 @@
-# This is a Databricks asset bundle definition for {{.project_name}}.
+# This is a Declarative Automation Bundle definition for {{.project_name}}.
 {{- if .auto_migration}}
 # The file was generated automatically by the Databricks extension. 
 # It's based on the configuration located in `.databricks/project.json`.

diff --git a/packages/databricks-vscode/resources/whats-new/2.4.md b/packages/databricks-vscode/resources/whats-new/2.4.md
@@ -4,18 +4,18 @@
 
 ## What's new?
 
--   [Databricks Asset Bundles support](#dabs)
+-   [Declarative Automation Bundles support](#dabs)
 -   [Bundle configuration](#dabs-config)
 -   [No environment variables in terminals](#no-env)
 
-### <a id="dabs"></a> Databricks Asset Bundles support
+### <a id="dabs"></a> Declarative Automation Bundles support
 
-The extension now supports [Databricks Asset Bundles](https://docs.databricks.com/en/dev-tools/bundles/index.html)! New features include:
+The extension now supports [Declarative Automation Bundles](https://docs.databricks.com/en/dev-tools/bundles/index.html)! New features include:
 
--   Easy authentication and configuration of your Databricks Asset Bundles through the Visual Studio Code UI, including **AuthType** profile selection.
+-   Easy authentication and configuration of your Declarative Automation Bundles through the Visual Studio Code UI, including **AuthType** profile selection.
 -   A **Target** selector in the Databricks extension panel to quickly switch between bundle target environments.
 -   The **Override Jobs cluster** in bundle option in the extension panel to enable easy cluster override.
--   A **Bundles Resource Explorer** view, which allows you to browse your bundle resources using the Visual Studio Code UI, deploy your local Databricks Asset Bundle’s resources to your remote Databricks workspace with a single click, and go directly to your deployed resources in your workspace from Visual Studio Code.
+-   A **Bundles Resource Explorer** view, which allows you to browse your bundle resources using the Visual Studio Code UI, deploy your local Declarative Automation Bundle’s resources to your remote Databricks workspace with a single click, and go directly to your deployed resources in your workspace from Visual Studio Code.
 -   A **Bundles Variables View**, which enables you to browse and edit your bundle variables using the Visual Studio Code UI. See Bundle Variables View.
 
 See [our documentation for more information](https://docs..databricks.com/dev-tools/vscode-ext/bundles.html).
@@ -24,7 +24,7 @@ See [our documentation for more information](https://docs..databricks.com/dev-to
 
 The extension now requires a bundle configuration to be present in the project.
 
-If you don't use Databricks Asset Bundles, the extension will ask you to "migrate" your project. This will only create a `databricks.yml` configuration file with your workspace url.
+If you don't use Declarative Automation Bundles, the extension will ask you to "migrate" your project. This will only create a `databricks.yml` configuration file with your workspace url.
 
 If you used our extension for a project before, we will migrate it automatically.
 

diff --git a/packages/databricks-vscode/src/bundle/BundleProjectManager.ts b/packages/databricks-vscode/src/bundle/BundleProjectManager.ts
@@ -205,7 +205,7 @@ export class BundleProjectManager {
             recordEvent({success: false});
             this.setPendingManualMigration();
             const message =
-                "Failed to perform automatic migration to Databricks Asset Bundles.";
+                "Failed to perform automatic migration to Declarative Automation Bundles.";
             this.logger.error(message, error);
             const errorMessage = (error as Error)?.message ?? "Unknown Error";
             window.showErrorMessage(`${message} ${errorMessage}`);
@@ -262,7 +262,7 @@ export class BundleProjectManager {
 
     @onError({
         popup: {
-            prefix: "Failed to migrate the project to Databricks Asset Bundles",
+            prefix: "Failed to migrate the project to Declarative Automation Bundles",
         },
     })
     public async startManualMigration() {

diff --git a/packages/databricks-vscode/src/bundle/BundleSchema.ts b/packages/databricks-vscode/src/bundle/BundleSchema.ts
@@ -41,7 +41,7 @@ export interface BundleSchema {
      */
     resources?: ResourcesClass | string;
     /**
-     * The identity to use when running Databricks Asset Bundles workflows.
+     * The identity to use when running Declarative Automation Bundles workflows.
      */
     run_as?: BundleSchem6 | string;
     /**

diff --git a/packages/databricks-vscode/src/ui/docs-view/DocsViewTreeDataProvider.ts b/packages/databricks-vscode/src/ui/docs-view/DocsViewTreeDataProvider.ts
@@ -69,7 +69,7 @@ export class DocsViewTreeDataProvider
                 type: "configuration_guide",
             },
             {
-                label: "Work with Databricks Asset Bundles",
+                label: "Work with Declarative Automation Bundles",
                 path: "dev-tools/vscode-ext/bundles",
                 type: "bundles_guide",
             },