Add missing fields to DbtInvocationSchema - #2327
Conversation
|
👋 @vyagubov |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan includes up to 8 reviews per rolling hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe changes add optional ChangesInvocation compatibility
Estimated code review effort: 3 (Moderate) | ~15 minutes Merge Risk: ⚪ Minimal · up to This change adds invocation metadata needed by the UI, and no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Documentation says
Elementary reads those variables from dbt
--vars. Also, there is a UI code to show the values.But DbtInvocationSchema doesn't carry those values, because fields are missing.
Aim is to get values to this UI form:

P.S. previous PR didn't get enough attention. That is why I made a fresh branch and rewrote the description.
Summary by CodeRabbit
New Features
Bug Fixes