Meltano should treat plugins as 'custom' if no variant is provided

[aaronsteers]

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&cid=C01TCRBBJD7

Originally posted by @WillDaSilva in #7296 (comment)

[tayloramurphy]

Since you mentioned the namespace issue:

• Make namespace optional in plugin definitions, auto-generate if missing #3296

[aaronsteers]

Thanks! I had that issue top of mind, but couldn't find the link. 😅

[stale]

This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.

[WillDaSilva]

Still relevant