Steve

Any follow-up to this @mateuszklimek? It's also difficult to install dbt_expectations along-side re-data as the moment I had to pin that to 0.5.8

Would be great if this was patched ``` packages: - package: dbt-labs/dbt_utils version: 0.9.4 - package: dbt-labs/dbt_external_tables version: 0.8.2 - package: dbt-labs/codegen version: 0.8.1 - package: brooklyn-data/dbt_artifacts version: 2.1.1 -...

with latest re-data/re_data: ``` Version error for package dbt-labs/dbt_utils: Could not find a satisfactory version from options: ['=0.9.4', '>=0.8.0', '=0.7.0', '

hi @NiallRees I was looking at this as we also want to use the freshness status. status is present in sources.yml, after `dbt source freshness` - and it does not...

Indeed that is the expectation. Not supplied = no effect on current settings. Only edge case probably is that on_create then the deployment is "on". In Prefect 1.x I believe...

@ChrisPaul33 I don't think the `build_from_flow()` method works that way for parameters... I think that would override intentionally. That is something that should be code-first - you want the settings...

It's possible to turn colours off.. thats what we do via a global dbt config setting. Still not as good as colours but at least cleans up the log abit....

What I'm considering is that now each deployment needs to be it's own file whilst this issue is outstanding. It will help in CI in that we now would only...

I've also found that when you pass a string to an s3 resource as the source, the performance for 5 deployments is very acceptable at say 12 seconds! But if...

I haven't done the logging but we use query tags extensively.. so I can see that yes indeed dbt is doing this for us as well. What's weird is that...