https://meltano.com/ logo
#cli
Title
# cli
f

flat-bear-81546

07/16/2021, 1:12 PM
Anyone else do this?
meltano install targetname
You must specify loader/extract blah blah arrrtgggg ok
meltano install loader targetname
Seems like meltano could be nice and if there's not duplicate tap/target names it could figure that out for you
2
😠 2
s

salmon-salesclerk-77709

07/16/2021, 2:28 PM
Explicit is better than implicit! 😄 But yeah it'd be cool to do some introspection on the name and just sort it out. Realistically we won't prioritize this ourselves but would love an MR 🙂
f

flat-bear-81546

07/16/2021, 2:35 PM
Thanks for the heads up! Seems like an easy win for someone 🙂
Appreciate the straight forwardness as always
s

salmon-salesclerk-77709

07/16/2021, 2:36 PM
Of course 😄
s

salmon-actor-23953

07/16/2021, 2:52 PM
I'll just second that - yes, I've also run into this with
meltano add
and
meltano install
. I certainly wouldn't mind if we had the logic to infer the type. Would be hard for us to prioritize, as Taylor mentions, but certainly would be a nice-to-have. I'm reminded of homebrew, the package manager for Macs. They used to require explicitly mentioning
cask
for GUI apps and then moved to
--cask
and now don't require it. The danger, there and here, is that while most are multually-exclusive, there's still a small chance of getting the wrong thing, For example, in Homebrew now you can get the wrong docker package if you
brew install docker
instead of
brew install --cask docker
- since there historically was a cask and non-cask version of it.
With taps and targets, its unlikely we'd see collision in names, but extended to other plugin types like utilities, validators, etc., there would be more likely of a name collision. We'd just need to be smart about finding and handling collisions.