Rename DLT to Lakeflow Declarative Pipelines in CLI docs and error messages (#3378)

shreyas-goenka · web-flow · commit 02f28447cc2d · 2025-08-08T15:14:43.000+02:00
Based on post merge comments in #3346
diff --git a/acceptance/bundle/deploy/pipeline/allow-duplicate-names/output.txt b/acceptance/bundle/deploy/pipeline/allow-duplicate-names/output.txt
@@ -46,7 +46,7 @@ Deployment complete!
 The following resources will be deleted:
   delete pipeline pipeline_one
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline pipeline_one
 
diff --git a/acceptance/bundle/deploy/pipeline/auto-approve/output.txt b/acceptance/bundle/deploy/pipeline/auto-approve/output.txt
@@ -43,8 +43,8 @@ delete pipelines.bar
 >>> errcode [CLI] bundle deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/[UNIQUE_NAME]/files...
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   delete pipeline bar
@@ -58,7 +58,7 @@ The following resources will be deleted:
   delete job foo
   delete pipeline bar
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline bar
 
diff --git a/acceptance/bundle/deploy/pipeline/recreate/output.txt b/acceptance/bundle/deploy/pipeline/recreate/output.txt
@@ -41,8 +41,8 @@ Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/[UNIQUE_NAME]/file
 This action will result in the deletion or recreation of the following UC schemas. Any underlying data may be lost:
   recreate schema bar
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   recreate pipeline foo
@@ -59,7 +59,7 @@ The following resources will be deleted:
 This action will result in the deletion of the following UC schemas. Any underlying data may be lost:
   delete schema bar
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline foo
 
diff --git a/acceptance/bundle/deploy/schema/auto-approve/output.txt b/acceptance/bundle/deploy/schema/auto-approve/output.txt
@@ -58,8 +58,8 @@ Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/[UNIQUE_NAME]/file
 This action will result in the deletion or recreation of the following UC schemas. Any underlying data may be lost:
   delete schema bar
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   recreate pipeline foo
@@ -75,7 +75,7 @@ The following resources will be deleted:
 This action will result in the deletion of the following UC schemas. Any underlying data may be lost:
   delete schema bar
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline foo
 
diff --git a/acceptance/bundle/destroy/all-resources/output.txt b/acceptance/bundle/destroy/all-resources/output.txt
@@ -13,7 +13,7 @@ The following resources will be deleted:
 This action will result in the deletion of the following UC schemas. Any underlying data may be lost:
   delete schema my_schema
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my_pipeline
 
diff --git a/acceptance/bundle/destroy/jobs-and-pipeline/output.txt b/acceptance/bundle/destroy/jobs-and-pipeline/output.txt
@@ -52,7 +52,7 @@ The following resources will be deleted:
   delete job foo
   delete pipeline bar
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline bar
 
diff --git a/acceptance/bundle/help/bundle-generate-pipeline/output.txt b/acceptance/bundle/help/bundle-generate-pipeline/output.txt
@@ -2,12 +2,12 @@
 >>> [CLI] bundle generate pipeline --help
 Generate bundle configuration for an existing Delta Live Tables pipeline.
 
-This command downloads an existing DLT pipeline's configuration and any associated
+This command downloads an existing Lakeflow Declarative Pipeline's configuration and any associated
 notebooks, creating bundle files that you can use to deploy the pipeline to other
 environments or manage it as code.
 
 Examples:
-  # Import a production DLT pipeline
+  # Import a production Lakeflow Declarative Pipeline
   databricks bundle generate pipeline --existing-pipeline-id abc123 --key etl_pipeline
 
   # Organize files in custom directories
diff --git a/acceptance/bundle/resources/pipelines/recreate/change-catalog/output.txt b/acceptance/bundle/resources/pipelines/recreate/change-catalog/output.txt
@@ -54,8 +54,8 @@ recreate pipelines.my
 >>> [CLI] bundle deploy --auto-approve
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/acc-[UNIQUE_NAME]/default/files...
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   recreate pipeline my
@@ -130,7 +130,7 @@ Exit code (musterr): 1
 The following resources will be deleted:
   delete pipeline my
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my
 
diff --git a/acceptance/bundle/resources/pipelines/recreate/change-ingestion-definition/output.txt b/acceptance/bundle/resources/pipelines/recreate/change-ingestion-definition/output.txt
@@ -59,8 +59,8 @@ recreate pipelines.my
 >>> [CLI] bundle deploy --auto-approve
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/acc-[UNIQUE_NAME]/default/files...
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   recreate pipeline my
@@ -146,7 +146,7 @@ Exit code (musterr): 1
 The following resources will be deleted:
   delete pipeline my
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my
 
diff --git a/acceptance/bundle/resources/pipelines/recreate/change-storage/output.txt b/acceptance/bundle/resources/pipelines/recreate/change-storage/output.txt
@@ -54,8 +54,8 @@ recreate pipelines.my
 >>> [CLI] bundle deploy --auto-approve
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/acc-[UNIQUE_NAME]/default/files...
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   recreate pipeline my
@@ -130,7 +130,7 @@ Exit code (musterr): 1
 The following resources will be deleted:
   delete pipeline my
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my
 
diff --git a/acceptance/bundle/resources/pipelines/update/output.txt b/acceptance/bundle/resources/pipelines/update/output.txt
@@ -70,7 +70,7 @@ Deployment complete!
 The following resources will be deleted:
   delete pipeline my
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my
 
diff --git a/acceptance/bundle/summary/modified_status/output.txt b/acceptance/bundle/summary/modified_status/output.txt
@@ -135,7 +135,7 @@ The following resources will be deleted:
 This action will result in the deletion of the following UC schemas. Any underlying data may be lost:
   delete schema my_schema
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my_pipeline
 
diff --git a/acceptance/bundle/templates/default-python/integration_classic/output.txt b/acceptance/bundle/templates/default-python/integration_classic/output.txt
@@ -88,7 +88,7 @@ The following resources will be deleted:
   delete job project_name_[UNIQUE_NAME]_job
   delete pipeline project_name_[UNIQUE_NAME]_pipeline
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline project_name_[UNIQUE_NAME]_pipeline
 
@@ -410,7 +410,7 @@ The following resources will be deleted:
   delete job project_name_[UNIQUE_NAME]_job
   delete pipeline project_name_[UNIQUE_NAME]_pipeline
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline project_name_[UNIQUE_NAME]_pipeline
 
diff --git a/acceptance/pipelines/deploy/auto-approve/output.txt b/acceptance/pipelines/deploy/auto-approve/output.txt
@@ -13,8 +13,8 @@ View your pipeline foo here: [DATABRICKS_URL]/pipelines/[UUID]?o=[NUMID]
 >>> errcode [PIPELINES] deploy
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-pipeline-auto-approve/default/files...
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   delete pipeline foo
@@ -27,8 +27,8 @@ Exit code: 1
 >>> [PIPELINES] deploy --auto-approve
 Uploading bundle files to /Workspace/Users/[USERNAME]/.bundle/test-pipeline-auto-approve/default/files...
 
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:
   delete pipeline foo
diff --git a/acceptance/pipelines/destroy/auto-approve/output.txt b/acceptance/pipelines/destroy/auto-approve/output.txt
@@ -16,7 +16,7 @@ Exit code: 1
 The following resources will be deleted:
   delete pipeline my_pipeline
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my_pipeline
 
diff --git a/acceptance/pipelines/destroy/destroy-pipeline/output.txt b/acceptance/pipelines/destroy/destroy-pipeline/output.txt
@@ -11,7 +11,7 @@ View your pipeline my_pipeline here: [DATABRICKS_URL]/pipelines/[UUID]?o=[NUMID]
 The following resources will be deleted:
   delete pipeline my_pipeline
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my_pipeline
 
diff --git a/acceptance/pipelines/destroy/force-lock/output.txt b/acceptance/pipelines/destroy/force-lock/output.txt
@@ -22,7 +22,7 @@ Exit code: 1
 The following resources will be deleted:
   delete pipeline foo
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline foo
 
diff --git a/acceptance/pipelines/e2e/output.txt b/acceptance/pipelines/e2e/output.txt
@@ -85,7 +85,7 @@ The following resources will be deleted:
   delete pipeline my_project_pipeline
   delete pipeline my_project_pipeline_2
 
-This action will result in the deletion of the following DLT Pipelines along with the
+This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:
   delete pipeline my_project_pipeline
   delete pipeline my_project_pipeline_2
diff --git a/bundle/phases/messages.go b/bundle/phases/messages.go
@@ -6,8 +6,8 @@ const (
 This action will result in the deletion or recreation of the following UC schemas. Any underlying data may be lost:`
 
 	deleteOrRecreateDltMessage = `
-This action will result in the deletion or recreation of the following DLT Pipelines along with the
-Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the Pipelines will
+This action will result in the deletion or recreation of the following Lakeflow Declarative Pipelines along with the
+Streaming Tables (STs) and Materialized Views (MVs) managed by them. Recreating the pipelines will
 restore the defined STs and MVs through full refresh. Note that recreation is necessary when pipeline
 properties such as the 'catalog' or 'storage' are changed:`
 
@@ -26,7 +26,7 @@ This will result in changed IDs and permanent URLs of the dashboards that will b
 const (
 	deleteSchemaMessage = `This action will result in the deletion of the following UC schemas. Any underlying data may be lost:`
 
-	deleteDltMessage = `This action will result in the deletion of the following DLT Pipelines along with the
+	deleteDltMessage = `This action will result in the deletion of the following Lakeflow Declarative Pipelines along with the
 Streaming Tables (STs) and Materialized Views (MVs) managed by them:`
 
 	deleteVolumeMessage = `This action will result in the deletion of the following volumes.
diff --git a/cmd/bundle/deployment/bind.go b/cmd/bundle/deployment/bind.go
@@ -31,7 +31,7 @@ Examples:
   # Bind a job resource to existing workspace job
   databricks bundle deployment bind my_etl_job 6565621249
 
-  # Bind a pipeline to existing DLT pipeline
+  # Bind a pipeline to existing Lakeflow Declarative Pipeline
   databricks bundle deployment bind data_pipeline 9876543210
 
   # Bind with automatic approval (useful for CI/CD)
diff --git a/cmd/bundle/generate/pipeline.go b/cmd/bundle/generate/pipeline.go
@@ -30,12 +30,12 @@ func NewGeneratePipelineCommand() *cobra.Command {
 		Short: "Generate bundle configuration for a pipeline",
 		Long: `Generate bundle configuration for an existing Delta Live Tables pipeline.
 
-This command downloads an existing DLT pipeline's configuration and any associated
+This command downloads an existing Lakeflow Declarative Pipeline's configuration and any associated
 notebooks, creating bundle files that you can use to deploy the pipeline to other
 environments or manage it as code.
 
 Examples:
-  # Import a production DLT pipeline
+  # Import a production Lakeflow Declarative Pipeline
   databricks bundle generate pipeline --existing-pipeline-id abc123 --key etl_pipeline
 
   # Organize files in custom directories
