Hey folks, when migrating to 2.0, is there a way t...
# plugins-general
j
Hey folks, when migrating to 2.0, is there a way to generate lock files for existing plugins? Do we just need to run
meltano add
for all of them again? Or do lock files only apply to discovered plugins?
a
This feature is coming very shortly. The files are created as downloads from the API endpoints, which themselves are adapted single-variant json versions of the Meltano discovery format. So, in the meanwhile as a workaround, you could very likely create you own lock files, but clearly this is not ideal. Are you looking to update your existing files or just ensure stability for your existing plugins? If the latter, then since the 2.x discovery.yml is now at end of life and won't receive further updates, you can consider this the "final" bundled discovery.yml and something of a lock file in itself, at least until each plugin is locked independently.
Here's the long term thinking: https://github.com/meltano/meltano/issues/5961
Probably will be
meltano lock my-plugin
, with options
--all
to lock all plugins and
--update
to get the latest version and replace the existing lock.
j
Thanks, this makes sense. I suppose since most of my plugins are
--custom
anyway the lock file won't accomplish much; most of that is already explicit in meltano.yml
p
I’ve heard that lockfiles exist now, but I haven’t been able to find documentation for this or how to generate one. Is there a way to generate a
constraints.txt
style file that specifies all the dependency version of a plugins’ dependencies now?