Repository navigation
Conversation
Bundle validate passed jobs the Jobs API rejects at deploy. Fixes databricks#7101.
|
Thanks for the contribution! This pull request was opened from a fork. If you're a member of the Databricks organization, please request access to the If you're an external contributor, no action is needed; a maintainer will review your pull request. |
The Jobs API applies the same condition requirement to each entry of the triggers list, so check those entries alongside the singular trigger. Add tests for the plural path and the ALL_UPDATED value.
|
Self-review follow-up in 663c8e9: the first version only checked the singular |
Cover a trigger without a table_update block and an empty table list, both of which must not report the multi-table condition error.
|
An authorized user can trigger integration tests manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
Changes
New read-only check that errors when a job trigger lists more than one table in table_names without setting condition. Registered in FastValidate so both bundle validate and bundle deploy catch it.
Why
Validate passed jobs the Jobs API rejects at deploy with a 400 after files are uploaded. Fixes #7101.
Error severity is deliberate: this shape always fails at deploy, so no working bundle can break.
Tests