Perform minimal update when --update is called with a new package

[weg-jr]

Say my project has the following files

environment.yml
virtual-packages.yml 
conda-linux-64.lock
conda-lock.yml

I want to add 1 new package with minimum required version updates to other packages similar to doing conda install in an existing environment. My assumption was that I could update environment.yml with the new package and then do the following:

conda-lock lock --update <new_package_name>

however this seems to trigger a full re-solve that bumps the version for all packages in environment

If I dont modify the environment.yml and run conda-lock lock --update <new_package_name> conda-lock will still re-solve the environment but it will fail to include the new package.

Is this a bug or is there something I am missing?

[maresb]

Hi @weg-jr, thanks for the question!

Your expectations are completely reasonable, and ideally conda-lock should behave the way you expect.

At the moment, --update is only for updating an existing package, not for installing a new package. At the very least, we should fail with a not-implemented error when --update is called on a package that's not already in the environment. And ideally we should do the minimal update that you expect.

In case you need this feature now, pixi has it, and it works very well.

[weg-jr]

Gotcha, thanks for the clarification. Pixi doesn't support some of the authentication methods I need but will keep an eye on it

[maresb]

Thanks! Let's rename this and track the desired behavior