#3381 Reconsider behavior when adding a custom plugin and utility of `--custom` Issue created by MeltyBot Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3459 Originally created by @tayloramurphy on 2022-05-03 145612 --- In https://gitlab.com/meltano/hub/-/issues/247+ @pnadolny13 and I were chatting about

--custom

for adding plugins. In the new world where MeltanoHub is the SSOT for installable plugins, requiring a

--custom

flag may not be critical. When a user attempts to add a plugin that MeltanoHub isn't aware of, we could have two optional paths: • assume they're installing a custom plugin and prompt the user for relevant inputs • immediately fail and say something like "plugin not found on MeltanoHub. Please check your inputs or re-run with

--custom

if this is a custom plugin I like the idea of the first option as it feels like a nicer experience. We could still keep the

--custom

flag for users which would essentially skip any network request to the Hub API and would just immediately drop them into the interactive setup. meltano/meltano