Improve pip target override condition with VENV_PIP_TARGET environment variable (bsc#1216850) #613
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Backport of saltstack/salt#65562
In case of specifyig
bin_env
thetarget
was populated fromVENV_PIP_TARGET
environment variable which is not really needed as most probably the it will require separate target for such case, and it's better to use the default for this particular binary environment with no overriding the target fromVENV_PIP_TARGET
Tracks: https://github.com/SUSE/spacewalk/issues/22982
Previous Behavior
Overrides
target
in case if it's not specified explicitly for all cases.New Behavior
Overrides
target
from the environment variable only ifbin_env
is not specified.Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes/No
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.