Skip to content

Allow referencing job libraries outside bundle root without the need to specify sync root - #2842

Merged
andrewnester merged 9 commits into
mainfrom
feature/libs-outside-root
Sep 3, 2025
Merged

Allow referencing job libraries outside bundle root without the need to specify sync root#2842
andrewnester merged 9 commits into
mainfrom
feature/libs-outside-root

Conversation

@andrewnester

Copy link
Copy Markdown
Contributor

Changes

Allow referencing job libraries outside bundle root without the need to specify sync root.

Previously it was failing with error indicating the libraries are not sync root, now it does not fail anymore.

Why

Libraries has their own upload cycle and do not rely on general bundle sync mechanism therefore it is not necessary to specify or check that libraries are in sync root.

Tests

Added acceptance tests

@andrewnester

Copy link
Copy Markdown
ContributorAuthor

Blocked until this merged and released and we have metrics gathered #2863

github-merge-queueBot pushed a commit that referenced this pull request May 13, 2025
## Changes
Emit warnings and metrics when path fallback is used
## Why
The fallback is pretty old and currently block the other feature changes
(#2842), so instead we'd prefer to
raise the warning and eventually remove the fallback
## Tests
Added acceptance tests
<!-- 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. -->
anton-107 pushed a commit that referenced this pull request May 14, 2025
## Changes
Emit warnings and metrics when path fallback is used
## Why
The fallback is pretty old and currently block the other feature changes
(#2842), so instead we'd prefer to
raise the warning and eventually remove the fallback
## Tests
Added acceptance tests
<!-- 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. -->
@github-actions

Copy link
Copy Markdown
Contributor

This PR has not received an update in a while. If you want to keep this PR open, please leave a comment below or push a new commit and auto-close will be canceled.

@pietern

Copy link
Copy Markdown
Contributor

@andrewnester This will resurrect once the path fallback has been removed, right?

@andrewnester

Copy link
Copy Markdown
ContributorAuthor

Yes, exactly, reopening it for now

@eng-dev-ecosystem-bot

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

Copy link
Copy Markdown
Collaborator

Run: 17432716714

Env✅​pass🔄​flaky🙈​skip
✅​aws linux308515
🔄​aws windows3063514
✅​aws-ucws linux420413
✅​aws-ucws windows421412
✅​azure linux308514
🔄​azure windows3072513
✅​azure-ucws linux420412
✅​azure-ucws windows421411
🔄​gcp linux3043516
🔄​gcp windows3053515
Test Nameaws windowsazure windowsgcp linuxgcp windows
TestAccept🔄​flaky✅​pass🔄​flaky🔄​flaky
TestAccept/bundle/resources/pipelines/update🔄​flaky✅​pass🔄​flaky🔄​flaky
TestAccept/bundle/resources/pipelines/update/DATABRICKS_CLI_DEPLOYMENT=direct-exp🔄​flaky🔄​flaky🔄​flaky🔄​flaky
TestAccept/bundle/resources/pipelines/update/DATABRICKS_CLI_DEPLOYMENT=terraform✅​pass🔄​flaky✅​pass✅​pass

@pieternpietern left a comment

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.

Can we rip out the fallback entirely?

@@ -0,0 +1,8 @@
# We run this test only locally for now because we need to figure out how to do
# bundle destroy on script.cleanup first.

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.

Why doesn't that work out of the box?

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.

Ah, I think it's just an old comment, but still doesn't make much sense to run this on cloud

for key, job := range t.b.Config.Resources.Jobs {
if job.GitSource != nil {
ignore = append(ignore, key)
}

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.

For later: libraries are never pulled from a Git source, IIRC, so translation still applies there...

@andrewnester

Copy link
Copy Markdown
ContributorAuthor

Can we rip out the fallback entirely?

I was planning to do it in the release after, for now, it would still work (aka show a useful error) for non library files such as notebooks for example

@andrewnester
andrewnester merged commit 863f940 into mainSep 3, 2025
12 of 13 checks passed
@andrewnester
andrewnester deleted the feature/libs-outside-root branch September 3, 2025 12:08
deco-sdk-taggingBot added a commit that referenced this pull request Sep 3, 2025
## Release v0.267.0
### CLI
* Introduce retries to `databricks psql` command ([#3492](#3492))
* Add rule files for coding agents working on the CLI code base ([#3245](#3245))
### Dependency updates
* Upgrade TF provider to 1.88.0 ([#3529](#3529))
* Upgrade Go SDK to 0.82.0
### Bundles
* Update default-python template to make DB Connect work out of the box for unit tests, using uv to install dependencies ([#3254](#3254))
* Add support for `TaskRetryMode` for continuous jobs ([#3529](#3529))
* Add support for specifying database instance as an application resource ([#3529](#3529))
* Allow referencing job libraries outside bundle root without the need to specify sync root ([#2842](#2842))
* Add top level `run_as` support for Lakeflow Declarative Pipelines ([#3307](#3307))
denik pushed a commit that referenced this pull request May 20, 2026
## Changes
Emit warnings and metrics when path fallback is used
## Why
The fallback is pretty old and currently block the other feature changes
(#2842), so instead we'd prefer to
raise the warning and eventually remove the fallback
## Tests
Added acceptance tests
<!-- 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
…to specify sync root (#2842)
## Changes
Allow referencing job libraries outside bundle root without the need to
specify sync root.
Previously it was failing with error indicating the libraries are not
sync root, now it does not fail anymore.
## Why
Libraries has their own upload cycle and do not rely on general bundle
sync mechanism therefore it is not necessary to specify or check that
libraries are in sync root.
## Tests
Added acceptance tests
<!-- 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.267.0
### CLI
* Introduce retries to `databricks psql` command ([#3492](#3492))
* Add rule files for coding agents working on the CLI code base ([#3245](#3245))
### Dependency updates
* Upgrade TF provider to 1.88.0 ([#3529](#3529))
* Upgrade Go SDK to 0.82.0
### Bundles
* Update default-python template to make DB Connect work out of the box for unit tests, using uv to install dependencies ([#3254](#3254))
* Add support for `TaskRetryMode` for continuous jobs ([#3529](#3529))
* Add support for specifying database instance as an application resource ([#3529](#3529))
* Allow referencing job libraries outside bundle root without the need to specify sync root ([#2842](#2842))
* Add top level `run_as` support for Lakeflow Declarative Pipelines ([#3307](#3307))
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.

3 participants

@andrewnester@pietern@eng-dev-ecosystem-bot