Allow passing through safety args, to work around pyup unreliability #3877
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.
The issue
#2825
This issue has not been fully solved by the ability to provide a key - pyup sometimes goes down, and it usually takes a long time. Since
pipenv check
is the only would-be-fast way to test if apipenv install
is needed, this limits its usability.The fix
This pull request adds a couple more arguments to pass through to safety, exposing its existing configuration options. It also adds an option to completely skip invoking
safety
, for cases were package installation checks and package security checks need to be run separately.Because it's a trivial change, I also changed the return code to
2
onsafety
failure.