I’m having a library and I want that when a change to this library is made, for this change to be picked up automatically by my production pipeline - python transforms written in a code repository.
Is it possible ?
To my understanding, this is not possible and that’s a a feature and not a bug: a library change won’t impact a production pipeline without a manual intervention (by triggering the checks on the backing repository). Dependencies are resolved statically at checks time.
Hey Vincent, you’re right on. Once a python transform generates an environment, we create a lockfile containing the full environment specifications of environment, to guarantee consistency between runs.
If you want to get newer dependencies you can follow one of two ways:
- explicitely declare the new version of the library you want using the libraries tab or by manipulating directly the “meta.yaml file”
- by corrupting the hash at the bottom of the lockfile (which is a hidden file in the repository), this will trigger a new environment computation which, unless not possible, will pick the newest compatible available releases of the specified libraries.
1 Like