Update product names: Workflows→Jobs, Delta Live Tables→Spark Declarative Pipelines by lennartkats-db · Pull Request #4967 · databricks/cli

lennartkats-db · 2026-04-14T11:28:43Z

Changes

Rename "Databricks Workflows" / "Workflows" → "Databricks Jobs" / "Jobs" in CLI help text and templates
Rename "Delta Live Tables" → "Spark Declarative Pipelines" and "DLT" → "SDP" in descriptions, comments, and schema annotations
Rename template parameter include_dlt → include_sdp and file dlt_pipeline.ipynb → sdp_pipeline.ipynb in experimental-jobs-as-code template

…tive Pipelines Update all non-generated references to retired product names: - "Databricks Workflows" / "Workflows" → "Databricks Jobs" / "Jobs" - "Delta Live Tables" → "Spark Declarative Pipelines" - "DLT" → "SDP" (in comments/internal code) - Template parameter `include_dlt` → `include_sdp` - Template file `dlt_pipeline.ipynb` → `sdp_pipeline.ipynb` Generated files (schema JSON, docsgen, acceptance test outputs, Python models) are not updated here — regenerate with `make schema`, `make docs`, `make test-update`, `make test-update-templates`, `make -C python codegen` after the upstream proto changes land. Co-authored-by: Isaac

Co-authored-by: Isaac

With include_pipeline properly wired (was silently ignored as include_dlt), PIPELINE=no now excludes the pipeline resource. With only a job resource, dynamic_version causes 1 change and 0 unchanged, which is correct behavior. Co-authored-by: Isaac

The template renamed include_dlt to include_pipeline in a prior PR, but the combinations test intentionally still passes include_dlt (which gets silently ignored, defaulting to yes). Renaming to include_pipeline makes PIPELINE=no actually exclude pipelines, causing divergent output across variants which the combinations framework doesn't support. Co-authored-by: Isaac

The output was corrupted when running tests locally without terraform, replacing the successful deployment output with terraform init errors. Restores correct output from main and applies DLT→SDP string change. Co-authored-by: Isaac

simonfaltum

Review swarm: Isaac + Cursor (1 round, Cursor timed out)

0 Critical | 1 Major (Gap) | 1 Nit | 1 Suggestion

The rename changes look correct across the board. A few things worth addressing before merge, the main one being that jsonschema.json appears to be manually edited rather than regenerated from the source annotations. There are also a couple of downstream generated files (jsonschema_for_docs.json, docsgen/output/reference.md, docsgen/output/resources.md) that still contain the old product names.

See inline comments for specifics.

simonfaltum · 2026-04-16T11:08:23Z

                    },
                    "additionalProperties": false,
-                    "markdownDescription": "The pipeline resource allows you to create Delta Live Tables [pipelines](https://docs.databricks.com/api/workspace/pipelines/create). For information about pipelines, see [link](https://docs.databricks.com/dlt/index.html). For a tutorial that uses the Declarative Automation Bundles template to create a pipeline, see [link](https://docs.databricks.com/dev-tools/bundles/pipelines-tutorial.html)."
+                    "markdownDescription": "The pipeline resource allows you to create Spark Declarative [Pipelines](https://docs.databricks.com/api/workspace/pipelines/create). For information about pipelines, see [link](https://docs.databricks.com/dlt/index.html). For a tutorial that uses the Declarative Automation Bundles template to create a pipeline, see [link](https://docs.databricks.com/dev-tools/bundles/pipelines-tutorial.html)."


[Gap (Major)] This file looks like it was manually edited rather than regenerated from the source annotations. That's fragile and can drift.

I think you should only edit the source files (annotations.yml, annotations_openapi_overrides.yml) and then run make schema && make schema-for-docs && make docs to regenerate everything consistently. The other generated files (jsonschema_for_docs.json, docsgen/output/reference.md, docsgen/output/resources.md) still contain the old product names and would get picked up by regeneration.

simonfaltum · 2026-04-16T11:08:23Z

  "_":
    "markdown_description": |-
-      The pipeline resource allows you to create Delta Live Tables [pipelines](/api/workspace/pipelines/create). For information about pipelines, see [_](/dlt/index.md). For a tutorial that uses the Declarative Automation Bundles template to create a pipeline, see [_](/dev-tools/bundles/pipelines-tutorial.md).
+      The pipeline resource allows you to create Spark Declarative [Pipelines](/api/workspace/pipelines/create). For information about pipelines, see [_](/dlt/index.md). For a tutorial that uses the Declarative Automation Bundles template to create a pipeline, see [_](/dev-tools/bundles/pipelines-tutorial.md).


[Nit] The new text reads "create Spark Declarative [Pipelines](...)" which splits the product name across a link boundary. "Spark Declarative" on its own doesn't mean anything. The original worked because "Delta Live Tables" was a self-contained product name and "pipelines" was a generic noun.

Consider "create [Spark Declarative Pipelines](/api/workspace/pipelines/create)" to keep the full product name inside the link.

simonfaltum · 2026-04-16T11:08:23Z


-	// One or more DLT pipelines is being recreated.
-	if len(dltActions) != 0 {
+	// One or more SDP pipelines is being recreated.


[Suggestion] Nice rename from dltActions to pipelineActions. The comment here could match: since the variable already says "pipeline", you could simplify to // One or more pipelines is being recreated. and drop the "SDP" abbreviation.

juliacrawf-db

Similar to the comments I made on the DABs rename PR, from Dylan Vance:

In general, it's safer to say "Lakeflow Spark Declarative Pipelines" than just "Spark Declarative Pipelines", to avoid confusion.

The name of the feature is "Spark Declarative Pipelines". The resource that it creates is a "pipeline". Do not use "Spark Declarative Pipeline" or "Lakeflow Spark Declarative Pipeline", as this isn't a thing.
It's very similar to DABs creating a bundle.

juliacrawf-db · 2026-04-16T18:18:16Z

 For example, the default template would deploy a job called
 `[dev yourname] my_dbt_sql_job` to your workspace.
-You can find that job by opening your workpace and clicking on **Workflows**.
+You can find that job by opening your workpace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workpace and clicking on **Jobs**.

You can find that job by opening your workpace and clicking on **Jobs & Pipelines**.

juliacrawf-db · 2026-04-16T18:18:29Z

    For example, the default template would deploy a job called
    `[dev yourname] my_default_scala_job` to your workspace.
-    You can find that job by opening your workspace and clicking on **Workflows**.
+    You can find that job by opening your workspace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workspace and clicking on **Jobs**.

You can find that job by opening your workspace and clicking on **Jobs & Pipelines**.

juliacrawf-db · 2026-04-16T18:18:43Z

    For example, the default template would deploy a job called
    `[dev yourname] my_default_sql_job` to your workspace.
-    You can find that job by opening your workpace and clicking on **Workflows**.
+    You can find that job by opening your workpace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workpace and clicking on **Jobs**.

You can find that job by opening your workpace and clicking on **Jobs & Pipelines**.

juliacrawf-db · 2026-04-16T18:18:55Z

   For example, the default template would deploy a job called
   `[dev yourname] my_jobs_as_code_job` to your workspace.
-   You can find that job by opening your workspace and clicking on **Workflows**.
+   You can find that job by opening your workspace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workspace and clicking on **Jobs**.

You can find that job by opening your workspace and clicking on **Jobs & Pipelines**.

juliacrawf-db · 2026-04-16T18:19:07Z

 For example, the default template would deploy a job called
 `[dev yourname] {{.project_name}}_job` to your workspace.
-You can find that job by opening your workpace and clicking on **Workflows**.
+You can find that job by opening your workpace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workpace and clicking on **Jobs**.

You can find that job by opening your workpace and clicking on **Jobs & Pipelines**.

juliacrawf-db · 2026-04-16T18:19:18Z

    For example, the default template would deploy a job called
    `[dev yourname] {{.project_name}}_job` to your workspace.
-    You can find that job by opening your workspace and clicking on **Workflows**.
+    You can find that job by opening your workspace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workspace and clicking on **Jobs**.

You can find that job by opening your workspace and clicking on **Jobs & Pipelines**.

juliacrawf-db · 2026-04-16T18:19:32Z

    For example, the default template would deploy a job called
    `[dev yourname] {{.project_name}}_job` to your workspace.
-    You can find that job by opening your workpace and clicking on **Workflows**.
+    You can find that job by opening your workpace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workpace and clicking on **Jobs**.

You can find that job by opening your workpace and clicking on **Jobs & Pipelines**.

juliacrawf-db · 2026-04-16T18:19:46Z

   For example, the default template would deploy a job called
   `[dev yourname] {{.project_name}}_job` to your workspace.
-   You can find that job by opening your workspace and clicking on **Workflows**.
+   You can find that job by opening your workspace and clicking on **Jobs**.


Suggested change

You can find that job by opening your workspace and clicking on **Jobs**.

You can find that job by opening your workspace and clicking on **Jobs & Pipelines**.

lennartkats-db and others added 7 commits April 14, 2026 12:12

Regenerate acceptance test outputs for product name changes

2f72a10

Co-authored-by: Isaac

Regenerate JSON schema for annotation changes

d4c3378

Co-authored-by: Isaac

Merge branch 'main' into product-name-changes

766df90

lennartkats-db changed the title ~~[draft] Update product names: Workflows→Jobs, Delta Live Tables→Spark Declarative Pipelines~~ Update product names: Workflows→Jobs, Delta Live Tables→Spark Declarative Pipelines Apr 15, 2026

lennartkats-db requested a review from denik April 15, 2026 08:13

pietern approved these changes Apr 16, 2026

View reviewed changes

simonfaltum reviewed Apr 16, 2026

View reviewed changes

juliacrawf-db reviewed Apr 16, 2026

View reviewed changes

	You can find that job by opening your workpace and clicking on Jobs.
	You can find that job by opening your workpace and clicking on Jobs & Pipelines.

Conversation

lennartkats-db commented Apr 14, 2026

Changes

Uh oh!

simonfaltum left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juliacrawf-db left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants