Dependencies Resolver
Command line tool for downloading dependencies from a configuration file. The configuration file must follow the schema configured in config/schema .json.
You can also specify the exact path to the file if that was uploaded manually and not by the s3-uploader.
This is part of Onfido’s team blobs store project.
The purpose of this tool is to download the project’s dependencies configured from a configuration file. Resources can be uploaded using the complimentary tool the s3-uploader.
Installing
$ pip install dependencies-resolver
How to use
Example for using the tool
dependencies-resolver -c dependencies.json
Get the project
Clone the git repository
$ git clone https://github.com/onfido/dependencies-resolver
Install a virtualenv
$ sudo apt-get install python-virtualenv
Create a new virtualenv
$ virtualenv dependencies_resolver_ve
Install project’s requirements
$ dependencies_resolver_ve/bin/pip install -r requirements.txt
Reporting Issues
If you have suggestions, bugs or other issues specific to this library, open an issue, or just be awesome and make a pull request out of it.
Metadata
Release files for dependencies-resolver 0.0.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| dependencies-resolver-0.0.11.tar.gz | 11.8 kB | Without provenance | Details |
Release files / dependencies-resolver-0.0.11.tar.gz
| Download URL | dependencies-resolver-0.0.11.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7514743ae15d3d94a8a54f44107802f2b071a13f117da0ed24508318ae27263
|
|
BLAKE2b-256 checksum How to use checksums |
6c65ebe636fe1e5ebd39954d0e1eb1e435fcadfb93dd6303c46c30256d6ffa67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dependencies-resolver 0.0.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.