#7305 Meltano should treat plugins as 'custom' if no `variant` is provided Issue created by aaronsteers on <!date^1676310698^{date_short}|2023-02-13T17:51:38Z> Note: • This is a 'bug' but also working as historically designed. I'm leaving 'bug' out of the title for now, but we can think of this either as a 'bug' or as a refactor to catch up with 2.0-related design changes. where

meltano.yml

was deprecated and the Hub and the lockfiles became primary source of record. Related to deprecation of

namespace

, this issue came up recently in #7296, where a plugin is reaching out to the Hub to find a plugin definition. If

variant

is not provided in the

meltano.yml

file, then searching for a lockfile will necessarily fail, as will the lookup to Hub. Hence, I think we can treat those as always 'custom'.

@edgarrmondragon @aaronsteers This may be caused by the

variant

not being specified in `meltano.yml`: https://meltano.slack.com/archives/C01TCRBBJD7/p1676044092702169?thread_ts=1675952792.259879&amp;cid=C01TCRBBJD7

Originally posted by @WillDaSilva in #7296 (comment)

meltano/meltano