8000 [Feature Request] DABs: allow target specific includes · Issue #2878 · databricks/cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Feature Request] DABs: allow target specific includes #2878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Escoto opened this issue May 14, 2025 · 1 comment
Open

[Feature Request] DABs: allow target specific includes #2878

Escoto opened this issue May 14, 2025 · 1 comment

Comments

@Escoto
Copy link
Escoto commented May 14, 2025

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.
@sdheepakdba
Copy link

We also required similar feature in Kaiser Environment

@andrewnester andrewnester marked this as a duplicate of #2872 May 28, 2025
This was referenced May 28, 2025
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Escoto @sdheepakdba
0