Hi Team, we're facing the following scenario. Let'...
# infra-deployment
q
Hi Team, we're facing the following scenario. Let's say we have the meltano project with this yaml file:
Copy code
plugin:
  utilities:
    - name: plugin_A
      pip_url: plugin_A==1.2.3
The open-source
plugin_A
has the following dependency constraints:
Copy code
lib_A='>=1.1.2,<=1.5.6'
lib_B='>=1.2.3,<=2.0.0'
...
Other than manually pining this
plugin_A
's dependency version in the pip_url (e.g
pip_url: plugin_A==1.2.3 lib_A==1.2.3
), is there a way to pin the full dependency tree for each plugin in a Meltano project? Is there any supported way to generate or use a lockfile for plugin dependency management? Otherwise, every time we install the plugins with
meltano install
(a step in our dockerfile), it will always install the latest versions of the plugin's dependencies within the range. We don't want this because it makes our deployment unstable sometime. Thank you in advance for any upcoming help! 🙏
r
There is a long-standing issue for this: https://github.com/meltano/meltano/issues/6416
🙏 1
➕ 1