[Feature Request] DABs: allow target specific includes

Open
  • Is something wrong?
#2,878 8 comments 15 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@andrewnester is already working on this.

Since Jun 23, 2025.

Assessment

This issue has not been assessed yet.

Description

DABs Enhancement No Autoclose

I am currently working on a project in the pharmaceutical sector within a GxP-validated environment. Operating under GxP (Good Practice) standards means we must exercise rigorous control over everything that is deployed across our environments development, staging, and production. Each of which has its own dedicated workspace. This heightened scrutiny is essential, as GxP compliance is not optional but a legal and regulatory requirement designed to ensure the safety, quality, and integrity of pharmaceutical products at every stage of their lifecycle.

Every deployment must meet strict validation and documentation standards, as even minor deviations can have significant regulatory and patient safety implications. This approach safeguards not only our compliance with global authorities such as the FDA and EMA, but also the trust of patients and healthcare providers who rely on the quality and safety of our products.

So, we are looking for a feature like:

A - Flexibility to have Workspace specific includes

targets:
  dev_01:
    include:
      - workflows/dev_01/*.yml

B - Ability to interpolate a directory in the Includes
Something like

include:
  - workflows/{bundle.target}/*.yml

Currently, our workaround involves creating multiple databricks.yml files and renaming them during CD, depending on the target environment. While this approach allows us to move forward, it is ultimately a stopgap rather than a robust solution.

In the pharmaceutical industry, GxP Validation is not just a standard process-it’s a critical requirement that ensures compliance, data integrity, and patient safety across the sector. This need for flexible environment configuration is not unique to our team; it’s a recurring challenge across various use cases in the industry. Implementing a more streamlined and scalable solution would deliver significant value. Not only to us but to the entire pharmaceutical sector-by enhancing efficiency, reducing risk, and supporting industry-wide best practices.

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.