Hi @maikel,

Have you considered using target‑scoped resources so that the jobs for specific notebooks only exist in the dev target and are simply not defined for pre-prod and prod?

Databricks Asset Bundles let you put a targets: block inside each resource file, and only the resources listed for the active target are deployed.

See below references... Explains how databricks.yml is structured, and how targets can override or add their own resources. This is the basis for "only define some resources for certain targets."

• AWS: Databricks Asset Bundle configuration
• Azure: Databricks Asset Bundle configuration
• GCP: Databricks Asset Bundle configuration

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.