Open nicoddemus opened 1 year ago
Looks like a bug, thanks for the report!
Noticed that it is also changing the file extensions in the url
field from .conda
to .tar.bz2
, which renders the lock file unusable. I've updated the title and description accordingly. 👍
Checklist
What happened?
Hi folks!
First of all thanks for the amazing tool!
At work we are using private channels with an embeded token via an environment variable.
When we create the lock file the first time, it correctly embeds the token environment variable in each package URL. However, when we call
--update
, it strips the authentication token from all URLs.Is this a bug or are we using
conda-lock
incorrectly?Reproducer:
This generates the
conda-lock.yml
file correctly, with each URL containing the environment variable embeded:Note the
url: https://$ESSS_CONDA_CHANNEL_TOKEN@eden.esss.co/conda-channel/mirror-conda-forge/noarch/boltons-23.0.0-pyhd8ed1ab_0.conda
line.However when we execute:
All the
$ESSS_CONDA_CHANNEL_TOKEN
strings are stripped from the individual package urls:Note the
url: https://eden.esss.co/conda-channel/mirror-conda-forge/noarch/boltons-23.0.0-pyhd8ed1ab_0.tar.bz2
line: the environment variable has been stripped, and the extension changed from.conda
to.tar.bz2
.Conda Info
Conda Config
Conda list
Additional Context
No response