What is the relationship between

transforms

and

transformers

? The docs are a little thin here (https://meltano.com/docs/transforms.html#dbt-data-build-tool-installation-and-configuration`). My first thought was that

transform

was just an invocation of the

transformer

(i.e install a single dbt project, globally, then change

config.models

section to invoke it for different transforms). But it looks like the relationship might be a bit more complicated? I was able to get my external dbt project loaded and executable via

meltano invoke dbt run -m my_external_project

simply by adding it to

transform/packages.yml

, though. So that was pretty neat

transforms

are a weird wrapper around dbt packages. I think we'll be moving away from recommended transforms as a way of managing dbt packages.

Very keen to understand the plan if you are going to move away from ‘transforms’. Would this be a topic of a meeting soon?