Skip to content

Relative path is not working within artifacts #1927

Description

@jiropardo

Describe the issue

Trying to deploy an artifcat referencing a location from an upstream folder when building an artifact using Relative path fails with a path resoultion error

Configuration

Please provide a minimal reproducible configuration for the issue

Steps to reproduce the behavior

Please list the steps required to reproduce the issue, for example:

1 Init a bundle , select python template , include python packae

  1. Create an upstream folder with build files upstream to the databricks.yml file
    ├── lib
    │ ├── setup.py
    │ └── src
    ├── cus_test
    │ │
    │ └── test_x
    │ │
    │ ├── setup.py
    │ └── src
    │ │
    │ ├── databricks.yml

databricks.yml file

bundle:
name: test_x
targets:
dev:
mode: production
default: true
workspace:
host: https://xxxxXXXXXX.cloud.databricks.com
artifact_path: /Shared/.artifacts/${bundle.name}
artifacts:
default:
type: whl
build: python3 setup.py bdist_wheel
path: .
lib:
type: whl
build: python3 setup.py bdist_wheel
path: ../../lib
sync:
paths:
- ../../lib
- .

If I use absolute path in the artifacts path, it works with no issues

artifacts:
default:
type: whl
build: python3 setup.py bdist_wheel
path: /Users/admin/Documents/tests/bundle/path_resolution/cus_test/test_x
lib:
type: whl
build: python3 setup.py bdist_wheel
path: /Users/admin/Documents/tests/bundle/lib

Expected Behavior

Path error should have not come up and they deployment should end up successfully

Actual Behavior

Clear and concise description of what actually happened
It give a path resolution error

OS and CLI version

Please provide the version of the CLI (eg: v0.1.2) and the operating system (eg: windows). You can run databricks --version to get the version of your Databricks CLI

Databricks CLI v0.234.0

Is this a regression?

Did this work in a previous version of the CLI? If so, which versions did you try? Never worked, not even in pre release CLI

Debug Logs

Output logs if you run the command with debug logs enabled. Example: databricks bundle deploy --log-level=debug. Redact if needed

Building default...
09:59:10 ERROR Error: build failed default, error: chdir /Users/admin/Documents/tests/bundle/path_resolution/cus_test/test_x/cus_test/test_x: no such file or directory, output: pid=59588 mutator=seq mutator=build mutator=seq mutator=artifacts.BuildAll mutator=seq mutator=artifacts.Build(default) mutator=seq mutator=artifacts.whl.Build(default)

Metadata

Metadata

Assignees

Labels

BugSomething isn't workingDABsDABs related issuesNo Autoclose

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions