Skip to content
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.

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

Use different resources.yaml at a target level #2102

Open
hariaculeti opened this issue Jan 9, 2025 · 0 comments
Open

Use different resources.yaml at a target level #2102

hariaculeti opened this issue Jan 9, 2025 · 0 comments
Labels
DABs DABs related issues

Comments

@hariaculeti
Copy link

hariaculeti commented Jan 9, 2025

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

@hariaculeti hariaculeti added the DABs DABs related issues label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DABs DABs related issues
Projects
None yet
Development

No branches or pull requests

1 participant