Skip to content

Added new Lakeflow Pipelines support for bundle generate - #3568

Merged
andrewnester merged 9 commits into
mainfrom
feat/generate-lakeflow-pipelines
Sep 17, 2025
Merged

Added new Lakeflow Pipelines support for bundle generate#3568
andrewnester merged 9 commits into
mainfrom
feat/generate-lakeflow-pipelines

Conversation

@andrewnester

@andrewnesterandrewnester commented Sep 8, 2025

Copy link
Copy Markdown
Contributor

Changes

Added new Lakeflow Pipelines support for bundle generate

Why

Now if the pipeline refers to root_path we download the whole content of it and rewrite any related libraries.glob paths pointing to the same remote paths to the local ones

Tests

Added an acceptance test

Confirmed that they can be deployed here: #3578

@eng-dev-ecosystem-bot

eng-dev-ecosystem-bot commented Sep 8, 2025

Copy link
Copy Markdown
Collaborator

Run: 17800399286

Env✅​pass🙈​skip
✅​aws linux311528
✅​aws windows312527
✅​aws-ucws linux423426
✅​aws-ucws windows424425
✅​azure linux311527
✅​azure windows312526
✅​azure-ucws linux423425
✅​azure-ucws windows424424
✅​gcp linux310529
✅​gcp windows311528

name: lakeflow-pipeline
libraries:
- glob:
include: ../pipeline/transformations/**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might be something for a followup, but pipeline source code should be in the same folder as the pipeline definiton for Lakeflow. So this should always say transformations/**. See also #3558.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is configured by use of --config-dir and --source-dir flags in bundle generate command and for this specific test I set them up in such a way that it also tests that all complex relative paths are resolved correctly.

This is not an example of how configuration should look like though

include: ../pipeline/transformations/**
- glob:
include: /Workspace/Users/foo@databricks.com/another/**
root_path: ../pipeline

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar to the above, the .yml file should be included in the root_path, so this should actually say . or maybe for clarity ".".

}

// Making sure the root path is relative to the config directory.
rel, err := filepath.Rel(configDir, sourceDir)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add an test case for this error as well?

@andrewnester
andrewnester added this pull request to the merge queueSep 16, 2025
@github-merge-queue
github-merge-queueBot removed this pull request from the merge queue due to failed status checks Sep 16, 2025
@andrewnester
andrewnester added this pull request to the merge queueSep 17, 2025
@andrewnester
andrewnester removed this pull request from the merge queue due to a manual request Sep 17, 2025
Merged via the queue into main with commit 6d2367fSep 17, 2025
13 checks passed
@andrewnester
andrewnester deleted the feat/generate-lakeflow-pipelines branch September 17, 2025 14:51
deco-sdk-taggingBot added a commit that referenced this pull request Sep 24, 2025
## Release v0.270.0
### Notable Changes
* Add 'databricks bundle plan' command. This command shows the deployment plan for the current bundle configuration without making any changes. ([#3530](#3530))
### Bundles
* Add 'databricks bundle plan' command ([#3530](#3530))
* Add new Lakeflow Pipelines support for bundle generate ([#3568](#3568))
* Fix bundle deploy to not update permissions or grants for unbound resources ([#3642](#3642))
* Introduce new bundle variable: `${workspace.current_user.domain_friendly_name}` ([#3623](#3623))
* Improve the output of bundle run when bundle is not deployed ([#3652](#3652))
denik pushed a commit that referenced this pull request May 20, 2026
## Changes
Added new Lakeflow Pipelines support for `bundle generate`
## Why
Now if the pipeline refers to `root_path` we download the whole content
of it and rewrite any related `libraries.glob` paths pointing to the
same remote paths to the local ones
## Tests
Added an acceptance test
Confirmed that they can be deployed here:
#3578
<!-- If your PR needs to be included in the release notes for next
release,
add a separate entry in NEXT_CHANGELOG.md as part of your PR. -->
denik pushed a commit that referenced this pull request May 20, 2026
## Release v0.270.0
### Notable Changes
* Add 'databricks bundle plan' command. This command shows the deployment plan for the current bundle configuration without making any changes. ([#3530](#3530))
### Bundles
* Add 'databricks bundle plan' command ([#3530](#3530))
* Add new Lakeflow Pipelines support for bundle generate ([#3568](#3568))
* Fix bundle deploy to not update permissions or grants for unbound resources ([#3642](#3642))
* Introduce new bundle variable: `${workspace.current_user.domain_friendly_name}` ([#3623](#3623))
* Improve the output of bundle run when bundle is not deployed ([#3652](#3652))
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@andrewnester@eng-dev-ecosystem-bot@lennartkats-db@shreyas-goenka