[DABs] Selective Key override for referencing complex variables

Open
#2,985 8 comments 3 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Start by tracing how DABs resolve complex variables and build resources.jobs.job_clusters. Use the YAML example to investigate whether a job-level num_workers override can be represented without redefining the full cluster, then identify the existing tests for variable resolution or job-cluster configuration. Done means selective overrides work for multiple jobs while preserving the shared complex variable.

Written by the indexing model from the issue text.

Description

DABs Enhancement

We defines the type primarily used in job clusters as a complex variable and manages its definition and distribution through DABs. However, we want to modify only certain variables of the complex variable based on the size or nature of the job, which is currently unsupported. As a result, they need to define each job cluster separately.
Their request is as follow. (override example of num_of_workers)

resources: 
   jobs: 
      aa:
         ...
         job_clusters:
         - job_cluster_key: default
            new_cluster: ${var.legacy-multi-node-job}
               num_workers: 1
      bb: ...
         job_clusters:
         - job_cluster_key: default
            new_cluster: ${var.legacy-multi-node-job}
               num_workers: 7

     ... # many jobs with different num of workers
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/cli

All issues in databricks/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.