[MartijnVermeulen96]

Changes

Apply presets.trigger_pause_status to each triggers[] entry on jobs, similar to how schedule, continuous & trigger are already handled. Only omitted values inherit the preset, so explicit per-trigger values are preserved. Development mode defaults the preset to PAUSED, so it is covered by the same change.

Why

With trigger_pause_status: PAUSED or mode: development, legacy schedules were paused but triggers[] entries were left without a pause status. The backend then defaults them to UNPAUSED, so dev deployments of jobs using the new field could start running on their schedule.

Tests

• Unit tests for PAUSED/UNPAUSED presets, explicit, mixed & unset values across cron, file arrival & table update triggers, plus development mode with & without an UNPAUSED preset.
• Acceptance test bundle/validate/presets_triggers_pause_status.
• Manually deployed two cron triggers to a staging workspace: both PAUSED under the preset & development mode, and an explicit UNPAUSED was kept after redeploy.

[github-actions]

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 cli-contrib team and open your pull request from a branch in this repository instead of a fork — fork PRs don't run integration tests automatically and have reduced CI access.

If you're an external contributor, no action is needed; a maintainer will review your pull request.

[github-actions]

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

• PR number: 7382
• Commit SHA: 7864e8947960d2e4faa2be419b107bbd6dc46481

Checks will be approved automatically on success.