GitHub
05/07/2026, 8:44 AMtransformer plugin to a Meltano Project that already has a transformer configured, additional files are added to the Projects /transform directory. This is a side-effect of adapter-specific dbt transformer plugins sharing a single dbt project directory (and associated files, such as dbt_project.yml.
What is the expected correct behavior?
When adding an additional transformer plugin, the associated file bundle should either be optional (user prompted) or omitted by default and a message displayed to invite the user to add the bundle manually (via meltano add files dbt-snowflake).
Steps to reproduce
# add the transformer dbt
meltano add transformer dbt
# add an additional transformer
meltano add transformer dbt-snowflake
Relevant logs and/or screenshots
Screenshot_2022-04-01_at_16.22.04
Screenshot_2022-04-01_at_16.24.47
Possible fixes
The logic for adding related plugins (including file bundles) is directly under the CLI add method. Ideally this would be adapted to include logic for handling the special case of transformer file bundles.
Alternatively, transformer file bundles could be namespaced, such that adding new transformers creates a new subfolder in the /transform directory (e.g. transform/dbt-snowflake/), to avoid clashes. This approach would likely impact the migration experience of existing users.
Further regression test
Ensure we automatically catch similar issues in the future
• Write additional adequate test cases and submit test results
• Test results should be reviewed by a person from the team
meltano/meltanoGitHub
05/07/2026, 8:44 AM