Is there an easy way to tell meltano I don’t want ...
# announcements
p
Is there an easy way to tell meltano I don’t want to install the default dbt transform packages, and just want to use my own?
d
@paul_blankley Where exactly are you seeing the default transform plugins enter the scene against your wishes/expectations?
p
Right after I run
meltano elt tap-shopify target-snowflake --transform only --job_id=shop22snow
if I don’t have the transform for shopify installed (which is desired, I want to use my own)
d
All right, did you add your own dbt models to
transform/models
, or as a transform plugin in
meltano.yml
?
Either path is supported, fwiw, and I'd consider this a bug no matter which way you went
@paul_blankley I've filed a new issue: https://gitlab.com/meltano/meltano/-/issues/2360
If you are bringing in your own models through a
transform
plugin, a workaround would be to make sure that the plugin is named
tap-slack
with namespace
tap_slack
, so that the default plugin is masked and overridden. If you're putting your models straight into
transform/models
, there's not currently a way to work around this issue, unfortunately.
Fortunately, addressing the issue I just linked should be pretty straight forward, and would only involve deleting code, not adding any 🙂 I hope to get to it next week, but if you happen to have time to look into it yourself, I may be able to get it out in an earlier release!
Another temporary workaround would be to add
tap-shopify
as a custom plugin with a
namespace
other than
tap_shopify
, so that the transform plugin won't be considered a related plugin in the first place.
p
sweet, I just submitted a PR!