Use different resources.yaml at a target level

[hariaculeti]

Describe the issue

How can I use different resources.yaml files (e.g., for pipelines, volumes, etc.) for different targets like dev or prod in DAB? For example, In my case, dev might have a single pipeline for a region, while prod could have multiple regions with corresponding pipelines.

one way is to hardcode all the pipelines and volumes directly in databricks.yaml but it becomes very hard to maintain.
Is there any other way to include specific resources.yaml files at the target level?

Configuration

not required

Steps to reproduce the behavior

Tried to use Include at a target level but didnt work.

Expected Behavior

NA

Actual Behavior

NA

OS and CLI version

NA

Is this a regression?

NA

Debug Logs

NA

[andrewnester]

Assuming you have files <target>.yml per all your targets which defined configuration and target overrides per each target you can safely include all the YAML files because DABs will use configuration only for the target you specified for deployment

[hariaculeti]

Ok, thanks Andrew From: Andrew Nester ***@***.***> Sent: Monday, 13 January 2025 11:43 PM To: databricks/cli ***@***.***> Cc: Aculeti, Hari (RTX) ***@***.***>; Author ***@***.***> Subject: [External] Re: [databricks/cli] Use different resources.yaml at a target level (Issue #2102) Assuming you have files <target>.yml per all your targets which defined configuration and target overrides per each target you can safely include all the YAML files because DABs will use configuration only for the target you specified for deployment - Reply to this email directly, view it on GitHub<#2102 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOWSNKQR35AH66WXGHITX6T2KO7FNAVCNFSM6AAAAABU3NA7BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXGEZTQOBQHE>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>