Add volume_path to the output for the volume object
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start with the databricks volumes list abc_catalog abc_schema entry point and locate the volume object output or serialization code. Check how the existing catalog, schema, and name fields are produced; done means the output also includes the expected /Volumes/{catalog}/{schema}/{name} path.
Written by the indexing model from the issue text.
Description
Describe the issue
Add volume_path to the output of the volume object:
{
"catalog_name": "abc_catalog",
"schema_name": "abc_schema",
"name": "abc_volume",
"volume_path": "/Volumes/abc_catalog/abc_schema/abc_volume"
}
Once this is done, DABs can be changed to use it like this:
parameters:
- name: abc_volume_path
default: ${resources.volumes.abc_volume_defn.volume_path}
Instead of:
default: /Volumes/${resources.volumes.abc_volume_defn.catalog_name}/${resources.volumes.abc_volume_defn.schema_name}/${resources.volumes.abc_volume_defn.name}
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
- Run
databricks volumes list abc_catalog abc_schema - Manually build the volume_path from the current output -- tedious.
Expected Behavior
Show the volume_path along with the other volume outputs
Actual Behavior
No volume_path provided, must be manually constructed from parts of the volume object.
With this provided in the output, DABs can then be updated to use something like this:
OS and CLI version
CLI: v0.255.0, any OS
Is this a regression?
No
- Dominant language
- Go
- Stars
- 427
- Forks
- 267
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 233
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databricks/cli
-
Apps commands only accept relative path to app.ymlPossibly taken @yuri-rod claimed this 38 days ago. OpenCLI
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
databricks/cli#6910 ·
Maintainers usually reply within 1 day
-
DABs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
databricks/cli#6670 · 1 reaction ·
Maintainers usually reply within 1 day
-
Bump vulnerable dependencies workflow is failingPossibly taken @shreyas-goenka claimed this today. Openbump-vuln-deps-failure
databricks/cli#7531 · 1 comment · 7 assignees ·
Maintainers usually reply within 1 day
-
bundle run on an app fails with "not in RUNNING state" when the app's compute is UPDATINGPossibly taken @andrewnester claimed this 1 day ago. OpenBug DABs
Difficulty 3/5 1-2 days Newbie friendliness 76/100
databricks/cli#7451 · 1 assignee ·
Maintainers usually reply within 1 day
-
Bundle deploy of an AI/BI dashboard breaks viewers' private bookmarks (UI save + publish does not)Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
databricks/cli#7419 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#6241 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coder/openstorage#807 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
NVIDIA/kubectl-nv#100 ·
Maintainers usually reply within 1 day
-
TestNoEagerPackageRegexps red on main: internal/gui/feedback.go:19 compiles a package-level regexpOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day