Usage
Documentation is hosted on ReadTheDocs.
Development
Multi-step workflows are defined as Task tasks. Run task --list to see them; the definitions live in .config/taskfiles/, and Taskfile.yaml in the repo root is only a shim that includes them.
This project has a dev container. If you already have VS Code and Docker installed, you can click the badge above or here to get started. Clicking these links will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
To publish a new version of the repository, you can run the Publish workflow manually and publish to the staging registry from any branch, and you can check the 'Publish to Primary' option when on main to publish to the primary registry and create a git tag.
The Release workflow reuses the checks from CI instead of re-running them: it requires that the CI workflow has already completed successfully for the current commit (including the workflow-summary job) and reuses the artifacts CI built rather than rebuilding. Trigger it manually with workflow_dispatch; a real release must be run from main, while the dry_run option lets you exercise the workflow from any branch without tagging or releasing. A real run publishes the CI-built distribution to the staging registry and verifies a fresh install, then pushes the v<version> git tag, publishes to the primary registry, verifies the install again, and finally creates a GitHub Release with auto-generated notes.
Open a connection to the EC2 instance hosting GBG Data Services in AWS:
aws ssm start-session --target i-0e5fd6d0bcdfd3c03 --document-name AWS-StartPortForwardingSession --parameters '{"portNumber":["8105"],"localPortNumber":["8105"]}'
When running the unit test suite, pytest-recording library is used. If it gives you errors about a cassette missing, the parameter to invoke a live HTTP request is --record-mode=once (add on to the end of the pytest command)
To run e2e tests locally against a specific data services version:
DATA_SERVICES_VERSION=1.6.2 uv run pytest tests/e2e
DATA_SERVICES_VERSION=2.0.0 uv run pytest tests/e2e
DATA_SERVICES_VERSION controls which Docker image docker-compose pulls. It defaults to 1.6.2 if unset.
Updating from the template
This repository uses a copier template. To pull in the latest updates from the template, run task copier-update
1 maintainer
Release files for biosero-data-services-sdk 0.13.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| biosero_data_services_sdk-0.13.2.tar.gz | 42.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| biosero_data_services_sdk-0.13.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 93.4 kB
Release files / biosero_data_services_sdk-0.13.2.tar.gz
| Download URL | biosero_data_services_sdk-0.13.2.tar.gz |
|---|---|
| Size | 42.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e7e4d63128426940067374a0ff6ad1ffa18ce4a2f08182f9a7f3603d73176da
|
|
BLAKE2b-256 checksum How to use checksums |
9893af23e080c5be1801da12d0b965ad6d39be97aab5f2610a0a0da360cfbb04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / biosero_data_services_sdk-0.13.2-py3-none-any.whl
| Download URL | biosero_data_services_sdk-0.13.2-py3-none-any.whl |
|---|---|
| Size | 50.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a8fca9105af85f35149c7c87cb7738b383008ac62c315f5362785ed6717f673
|
|
BLAKE2b-256 checksum How to use checksums |
cecdde0b1fab33b73da7734b8811a87c4ee5bd54d788459002c8292ef801a166
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
