pulsar-relay-client
Python client for the pulsar-relay HTTP wire contract.
Used by:
- the Pulsar daemon's relay subscriber/auth layer
- Galaxy's BYOC (Bring-Your-Own-Compute) Pulsar manager
- pulsar-relay's own end-to-end tests
The package is the single source of truth for the relay wire contract; the
server (pulsar-relay) and the client (pulsar-relay-client) version
independently. A new client version that knows about a new wire feature
bumps the minor version; breaking changes bump major.
Modules
| Module | Public surface |
|---|---|
pulsar_relay_client.auth |
RelayAuthManager, PasswordAuthenticator, RefreshTokenAuthenticator, RelayAuthError |
pulsar_relay_client.credentials |
CredentialsFile, InMemoryCredentialsStore, utcnow_iso |
pulsar_relay_client.device_flow |
RelayDeviceFlowAuthenticator, DeviceFlowError (RFC 8628 + the pair=true extension) |
pulsar_relay_client.transport |
RelayTransport, RelayTransportError (HTTP + auth + cursor persistence) |
pulsar_relay_client.topics |
HttpRelayClient with create_or_verify_topic, the RelayClient Protocol (caller-facing typing surface), and the relay-error hierarchy. Topic naming conventions are the caller's concern. |
pulsar_relay_client.testing |
FakeRelayClient — in-memory implementation of the RelayClient Protocol for consumers writing tests against a fake. |
Installation
pip install pulsar-relay-client
Quick start
from pulsar_relay_client import RelayTransport
transport = RelayTransport(
"https://relay.example.org",
credentials_file="/etc/pulsar/relay_credentials.json",
cursor_path="/var/lib/pulsar/relay_cursor.json",
)
transport.post_message("job_status_update_my_manager", {"job_id": "j1", "state": "ok"})
messages = transport.long_poll(["job_setup_my_manager"], timeout=30)
Versioning
1.0.0— first standalone release. Wire features: device-flow withpair=true, chain-scoped revocation, topic create-or-verify-ownership, refresh-token rotation withInMemoryCredentialsStorecallback.
Release files for pulsar-relay-client 0.2.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 | Provenance | Actions |
|---|---|---|---|---|
| pulsar_relay_client-0.2.2.tar.gz | 30.2 kB | With provenance | Details for pulsar_relay_client-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pulsar_relay_client-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for pulsar_relay_client-0.2.2-py3-none-any.whl |
Total release size: 55.7 kB
Release files / pulsar_relay_client-0.2.2.tar.gz
| Download URL | pulsar_relay_client-0.2.2.tar.gz |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e7ea1a5c2f2028a47f7c3364ce4b83458041edf35e8eb9816dd05a7efa4479f
|
|
BLAKE2b-256 checksum How to use checksums |
3850a6327fec07610fb2d06d2235658affc06931634caf834e195201637ff6ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 14, 2026.
Transparency logRelease files / pulsar_relay_client-0.2.2-py3-none-any.whl
| Download URL | pulsar_relay_client-0.2.2-py3-none-any.whl |
|---|---|
| Size | 25.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7fdf136cde4e9ce456abaf852690717116d372c7bd346c6b588b21d4d39f117f
|
|
BLAKE2b-256 checksum How to use checksums |
a093f7970157d60ef2f047810c73685f8227d9e7eab9d93a953db9c58370e028
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 14, 2026.
Transparency logSecurity for pulsar-relay-client 0.2.2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pulsar_relay_client-0.2.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 14, 2026.
Transparency logA 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.
