DAB dynvar: cannot parse resource keys starting with digits when permissions are set
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
Research direction
Start by tracing how the CLI parses resource references such as ${resources.jobs.00_clear_silver_and_gold.id} while planning resource permissions, then compare that path with the case where permissions are absent. Reproduce with the YAML example using databricks bundle plan or deploy; done when a resource key beginning with digits plans successfully with permissions.
Written by the indexing model from the issue text.
Description
Problem
Resource keys starting with a digit (e.g. 00_clear_silver_and_gold) fail with cannot parse when permissions are defined on the resource.
Error message:
Error: cannot plan resources.jobs.00_clear_silver_and_gold.permissions: cannot parse "/jobs/${resources.jobs.00_clear_silver_and_gold.id}" Error: planning failed
The same key works fine without permissions. Renaming the key to not start with a digit (e.g. clear_silver_and_gold) while keeping name: 00_clear_silver_and_gold resolves the issue.
Reproduction
CLI version: 1.7.0
resources:
jobs:
00_clear_silver_and_gold:
name: 00_clear_silver_and_gold
permissions:
- group_name: engineer-group
level: CAN_MANAGE
- group_name: admin-group
level: CAN_MANAGE
tasks:
- task_key: example_task
notebook_task:
notebook_path: ${workspace.file_path}/src/example
Running databricks bundle deploy or databricks bundle plan produces:
Error: cannot plan resources.jobs.00_clear_silver_and_gold.permissions: cannot parse "/jobs/${resources.jobs.00_clear_silver_and_gold.id}"
Expected behavior
Resource keys starting with digits should be supported, consistent with how Terraform and the Databricks API handle job names.
- 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 86/100
Maintainers usually reply within 1 day
-
kind/features
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
TencentBlueKing/bk-nodemgr#3991 ·
Maintainers usually reply within 1 day
-
meta
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
last9/last9-mcp-server#554 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Plain-http federation signing external_url fails startup with "invalid federation request signature"Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day