-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Password supplied via environment variable in environment.yaml
is expanded in conda-lock.yml
#594
Comments
Oh, that's bad. Thanks for the report. I will try to figure out what's going on. |
I'd like a reproducer that doesn't strictly rely on a private pypi repo. I tried this but failed to reproduce the problem:
|
Reference: #529 Noteworthy is the mock private pypi. |
Still trying to figure out what's going on. This problem should have been caught by this test: conda-lock/tests/test_pip_repositories.py Lines 164 to 172 in 2c2999b
@jacksmith15, do you have any insights? |
I've been executing my lock file generation in parallel to the test conda-lock/conda_lock/pypi_solver.py Line 361 in 431c09b
link diverges.
From the test:
From my case:
Where the Before conda-lock/conda_lock/pypi_solver.py Line 361 in 431c09b
op.package.source_url for both cases included the expanded password.
|
I got further. Here is a stack trace to a point in execution where I believes the problem lies:
When I'm running my use case, within that final call to I haven't given any though to a solution yet, but it seems to me that the test for my case is to change conda-lock/tests/test_pip_repositories.py Line 87 in 2c2999b
to
|
Checklist
What happened?
I have an
environment.yaml
:and I run:
The resulting
conda-lock.yml
contains the expanded value of the$CODEARTIFACT_PASSWORD
environmental variable. I expected this environment variable would not be expanded in theconda-lock.yml/
Conda Info
Conda Config
Conda list
Additional Context
I also tried supplying the the environmental variable inside
{}
:but there was no change in observed behavior.
The text was updated successfully, but these errors were encountered: