Skip to content

fix: refine dbtcloud_job type transition rules to avoid unnecessary replacement (closes #666)#668

Open
trouze wants to merge 3 commits into
mainfrom
fix/issue-666-job-type-transitions
Open

fix: refine dbtcloud_job type transition rules to avoid unnecessary replacement (closes #666)#668
trouze wants to merge 3 commits into
mainfrom
fix/issue-666-job-type-transitions

Conversation

@trouze
Copy link
Copy Markdown
Contributor

@trouze trouze commented Apr 9, 2026

Summary

  • Only CI↔non-CI and Adaptive↔non-Adaptive transitions now require resource replacement
  • Scheduled↔Other and Merge↔Other/Scheduled transitions allow in-place updates
  • Adds requiresJobTypeReplacement() helper function
  • Adds two new acceptance test functions for valid in-place and replacement transitions

Closes #666

🤖 Generated with Claude Code

…eplacement (closes #666)

Only CI<->non-CI and Adaptive<->non-Adaptive job type transitions now trigger
resource replacement. Scheduled<->Other and Merge<->Other/Scheduled transitions
are handled in-place. Adds requiresJobTypeReplacement() helper and two new
acceptance test functions.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@trouze trouze requested a review from a team as a code owner April 9, 2026 19:52
trouze and others added 2 commits April 9, 2026 14:58
The API infers job_type from triggers rather than honoring the explicit
field alone. Set schedule=true for scheduled jobs and on_merge=true for
merge jobs so the API returns the expected job_type value.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: refine dbtcloud_job type transition rules to avoid unnecessary resource replacement

1 participant