Iseq resources
Scripts that allow you to:
- Adding a new tool to the JSON file
- Iterating over the tools in the JSON file and checking the latest version, and in the case of a new version, adding a tooltip to JIRA
- Update existing tool/database record in JSON after updating tool/database
- Update docker-versions.json in workflows repository
Install
pip install iseqresources
Requirements
- python >=3.6
- jira >= 3.3.0
- requests >= 2.22.0
- python-gitlab >= 3.7.0
Adding a new tool
First specify if you want to add tool or database. Input JSON file (--input-json) is from gitlab repo at path json/tools.json or json/databases.json. Default is json/tools.json.
add_tool --tools
or
add_tool --databases
You can also run on a local file:
add_tool \
--input-json "/path/to/json/tools_or_databases.json"
It is better to add new tool directly to json file.
Checking versions and add task to JIRA
Input JSON file (--input-json and --info-json) are from gitlab repo at path json/tools.json or json/databases.json and json/info.json. Default is json/tools.json.
check_versions --tools
or
check_versions --databases
You can also run on a local files:
check_versions \
--input-json "/path/to/json/tools_or_databases.json" \
--info-json "/path/to/json/info.json"
Update existing tool/database record in JSON
Input JSON file (--input-json) is from gitlab repo at path json/tools.json or json/databases.json. Default is json/tools.json.
update_record --tools
or
update_record --databases
You can also run on a local file:
update_record \
--input-json "/path/to/json/tools_or_databases.json"
Update docker-versions.json in workflows repository (based on tools.json)
After updating tools.json at json/tools.json you need to get into root directory of workflows repository and type in bash:
update_docker_versions
For possible customization options and help use flag -h
update_docker_versions -h
Metadata
Release files for iseqresources 0.0.15
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 | |
|---|---|---|---|---|
| iseqresources-0.0.15.tar.gz | 11.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iseqresources-0.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.2 kB
Release files / iseqresources-0.0.15.tar.gz
| Download URL | iseqresources-0.0.15.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dc95d9ae6a61126036f005a1c285fa858b847f44c3240ee71de5e44a7d88ea3f
|
|
BLAKE2b-256 checksum How to use checksums |
4ec1345024c67614fe56191221f23dae96654b392a5695128bb437fdb375cb8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / iseqresources-0.0.15-py3-none-any.whl
| Download URL | iseqresources-0.0.15-py3-none-any.whl |
|---|---|
| Size | 14.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b595e27ae78c2584b3d3a8d7c140e66c0f6e57536d589de4c3456177f99b41c6
|
|
BLAKE2b-256 checksum How to use checksums |
ccfd0e418e3d590e470b403d3c09897a0519c1d9660ef6c60cfd48b586b8ea9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for iseqresources 0.0.15
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.