This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 2.399.0 instead.
This document defines the REST API for Data Repository. Status: design in progress There are four top-level endpoints (besides some used by swagger): * /swagger-ui.html - generated by swagger: swagger API page that provides this documentation and a live UI for submitting REST requests * /status - provides the operational status of the service * /api - is the authenticated and authorized Data Repository API * /ga4gh/drs/v1 - is a transcription of the Data Repository Service API The overall API (/api) currently supports two interfaces: * Repository - a general and default interface for initial setup, managing ingest and repository metadata * Resource - an interface for managing billing accounts and resources The API endpoints are organized by interface. Each interface is separately versioned. ## Notes on Naming All of the reference items are suffixed with "Model". Those names are used as the class names in the generated Java code. It is helpful to distinguish these model classes from other related classes, like the DAO classes and the operation classes. ## Editing and debugging I have found it best to edit this file directly to make changes and then use the swagger-editor to validate. The errors out of swagger-codegen are not that helpful. In the swagger-editor, it gives you nice errors and links to the place in the YAML where the errors are. But… the swagger-editor has been a bit of a pain for me to run. I tried the online website and was not able to load my YAML. Instead, I run it locally in a docker container, like this: ``` docker pull swaggerapi/swagger-editor docker run -p 9090:8080 swaggerapi/swagger-editor ``` Then navigate to localhost:9090 in your browser. I have not been able to get the file upload to work. It is a bit of a PITA, but I copy-paste the source code, replacing what is in the editor. Then make any fixes. Then copy-paste the resulting, valid file back into our source code. Not elegant, but easier than playing detective with the swagger-codegen errors. This might be something about my browser or environment, so give it a try yourself and see how it goes. ## Merging the DRS standard swagger into this swagger ## The merging is done in three sections: 1. Merging the security definitions into our security definitions 2. This section of paths. We make all paths explicit (prefixed with /ga4gh/drs/v1) All standard DRS definitions and parameters are prefixed with 'DRS' to separate them from our native definitions and parameters. We remove the x-swagger-router-controller lines. 3. A separate part of the definitions section for the DRS definitions NOTE: the code here does not relect the DRS spec anymore. See DR-409. # noqa: E501
Release files for data-repo-client 1
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 | |
|---|---|---|---|---|
| data_repo_client-1.tar.gz | 81.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| data_repo_client-1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 572.7 kB
Release files / data_repo_client-1.tar.gz
| Download URL | data_repo_client-1.tar.gz |
|---|---|
| Size | 81.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce951f705a9b0b5732f39678130517450df2fe1c883d933450a4cf9231eb7ddf
|
|
BLAKE2b-256 checksum How to use checksums |
de5b0e1cd69a7287b9834b26b2222734f7dabfd12b8853a1c0d902a6410a05e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.6
|
Release files / data_repo_client-1-py3-none-any.whl
| Download URL | data_repo_client-1-py3-none-any.whl |
|---|---|
| Size | 491.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4688eb0ae788e107d29e4d63b7aa6350fb8c8261c862c38c790fe32b01d79d14
|
|
BLAKE2b-256 checksum How to use checksums |
c64fd981ee336c7672d9decaf6396e45a0f31615ce7dd28d4e7a1d2b4dc31b82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.6
|
Security for data-repo-client 1
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.
