`meltano lock` -> variant 'original' is not known to Meltano
See original GitHub issueI’m getting the following error when I’m trying to run a meltano lock --all
on the squared project (note, I did first manually updated to remove executable and namespace which were defined in my project). When I commented out the inherit_from
children it works, the plugin is locked, then uncommenting the children again makes it fail again so I’m pretty sure its related to the inheriting.
File "/Users/pnadolny/.virtualenvs/meltano/lib/python3.8/site-packages/meltano/core/project_plugins_service.py", line 521, in get_parent
parent, source = self.find_parent(plugin)
File "/Users/pnadolny/.virtualenvs/meltano/lib/python3.8/site-packages/meltano/core/project_plugins_service.py", line 510, in find_parent
raise error
File "/Users/pnadolny/.virtualenvs/meltano/lib/python3.8/site-packages/meltano/core/project_plugins_service.py", line 505, in find_parent
return (self._get_parent_from_hub(plugin), DefinitionSource.HUB)
File "/Users/pnadolny/.virtualenvs/meltano/lib/python3.8/site-packages/meltano/core/project_plugins_service.py", line 441, in _get_parent_from_hub
return self.hub_service.get_base_plugin(plugin, variant_name=plugin.variant)
File "/Users/pnadolny/.virtualenvs/meltano/lib/python3.8/site-packages/meltano/core/plugin_discovery_service.py", line 136, in get_base_plugin
plugin = project_plugin.custom_definition or self.find_definition(
File "/Users/pnadolny/.virtualenvs/meltano/lib/python3.8/site-packages/meltano/core/hub/client.py", line 189, in find_definition
raise HubPluginVariantNotFound(
meltano.core.hub.client.HubPluginVariantNotFound: Extractor 'tap-github' variant 'original' is not known to Meltano. Variants: ['singer-io (default)', 'meltanolabs']
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/pnadolny/.virtualenvs/meltano/lib/python3.8/site-packages/meltano/cli/__init__.py", line 74, in _run_cli
raise CliError(str(err)) from err
meltano.cli.utils.CliError: Extractor 'tap-github' variant 'original' is not known to Meltano. Variants: ['singer-io (default)', 'meltanolabs']
Extractor 'tap-github' variant 'original' is not known to Meltano. Variants: ['singer-io (default)', 'meltanolabs']
Issue Analytics
- State:
- Created a year ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Complete Tutorial - Meltano Documentation
View and Activate Your Environments #. As part of creating your Meltano project, we automatically added your first environments called dev , staging...
Read more >Introduce plugin variants to support multiple versions of target ...
Existing Meltano projects using https://gitlab.com/meltano/target-snowflake explicitly reference it from their meltano.yml files using pip_url .
Read more >Airflow 1.10.x and 2.1.x broken when upgrading to Meltano ...
I'm having issues deploying to production my 2.0.2 version of meltano regarding airflow. My current version of airflow is 1.10.15 (not 2.
Read more >My Journey Towards Getting Started With Meltano - Medium
To do so, an extractor and a loader are added into our Meltano project called “getting-started”. We go through some useful settings against ......
Read more >meltano Archives - DataDuel.co
Now that new OLAP tools like DuckDB can take better advantage of that compute, horizontal scaling is no longer necessary for many analyses!...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tayloramurphy yup, that is right
@pnadolny13 Just to confirm, you’re saying that
meltano lock --all
worked with only this:But not when this was (re)added:
I wonder why in that first case with only
tap-github
, we didn’t hit the same error as https://github.com/meltano/meltano/issues/6360, which I’d expect any time there’s aname
but novariant
(and nonamespace
to indicate a custom plugin, orinherit_from
to indicate an explicitly inherited one).I don’t think we should recommend this:
namespace
is still supported and valuable, as it indicates custom plugins that shouldn’t be looked up on the Hub (see also https://github.com/meltano/meltano/issues/3296#issuecomment-1166157626 about why we can’t just remove that property).