Skip to content

for_each_task checks on databricks bundle validate - #4104

Open
idelafuente-oc wants to merge 8 commits into
databricks:mainfrom
idelafuente-oc:validate/for_each_task_validation
Open

idelafuente-oc wants to merge 8 commits into
databricks:mainfrom
idelafuente-oc:validate/for_each_task_validation

Conversation

@idelafuente-oc

@idelafuente-oc idelafuente-oc commented Dec 5, 2025 •

Copy link
Copy Markdown

Closes: #3977

Changes

Adds to the databricks bundle validate the ability to detect properties wrongly added to the parent task in for_each_task.
Currently it checks for:

  • max_retries (errors)
  • min_retry_interval_millis (warning)
  • retry_on_timeout (warning)

Can easily be extended to other configs with it's custom check.

Why

Currently databricks bundle validate doesn't detect this kind of issues, only on deployment this error was thrown. I think it's a good idea to add to the validate logic this typos of checks to prevent issues early on.

Tests

I have tested this changes by building the wheel locally with the changes implemented, here is the output of a validate run over code with the issue:
517134763-5a6f7f40-dbf6-408a-ad75-2765e25c73f4
I also added the unit tests for this.

Loading
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

Successfully merging this pull request may close these issues.

Validate doesn't detect issues on for_each_task

2 participants