The problem I’m having
We have added some authorized views models in our dbt project which is always triggered by state:modified together with defer for each env. This causes the selector with downstream or upstream dependencies to trigger a whole lot more models than anticipated.
The context of why I’m trying to do this
We want to use state:modified with down or upstream dependencies triggered in some CI jobs, but we only want to trigger those models that have been modified in that specific feature-branch / MR.
What I’ve already tried
One possible but ugly solution was to tag every authorized view model and exclude them in the runs. But then we don’t check that they work as intended when they have been modified…