[Feature Request] DABs: allow target specific includes

オープン
  • 何か問題がありますか？
#2,878 コメント 8 件 リアクション 15 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@andrewnester がすでに取り組んでいます。

2025年6月23日 から。

評価

この issue はまだ評価されていません。

説明

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.

主要言語
Go
スター
427
フォーク
267
平均マージ
2日 1時間
マージ済み PR（30日）
233

環境構築

  • Dockerfile または Docker Compose ファイルあり
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

databricks/cli のほかの issue

databricks/cli の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。