Skip to content

Conversation

@sshpuntoff
Copy link

## Changes
In a runtime container, I need to be able to reference files.
This PR allows the file:/// path (which is valid in databricks templates) to do that.
Currently the CLI attempts to resolve this path when it should now.

Open to feedback here.

Why

When running a containerized job, I have pre-bundled assets that need to be referenced.
If I set the path to file:/// manually via the databricks UX, my job works. If I attempt to do it via the cli, I have this rendering issue.

databricks bundle deploy --target dev
Error: file doesn't exist file:///opt/spark/jars/app.jar

With this change, the asset bundle is deployable.

Tests

Unit testing and manual deployment verification.

@github-actions
Copy link

github-actions bot commented Nov 7, 2025

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 3892
  • Commit SHA: a81c9166fb82d84faccd86a67497dd5c832bc0e6

Checks will be approved automatically on success.

Sign up for free to 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.

1 participant