ob-auth
Lightweight, zero-dependency Python client for authenticating with the Outerbounds platform.
Use ob-auth when you need to call Outerbounds deployment APIs programmatically
without pulling in the full metaflow or outerbounds packages.
Installation
pip install ob-auth
If you use IAM-based authentication (AWS Secrets Manager config), install the optional AWS extra:
pip install ob-auth[aws]
Usage
From local Metaflow config (laptop or inside a deployment)
from ob_auth import OuterboundsAuth
auth = OuterboundsAuth()
auth.init_from_config() # reads ~/.metaflowconfig/config.json
# If the config contains OBP_METAFLOW_CONFIG_URL, the full config
# is fetched remotely using the auth key from the same file.
import urllib.request, json
req = urllib.request.Request(
"https://api-c-xxxxx.your-domain.outerbounds.xyz/predict",
headers=auth.api_headers(),
)
resp = urllib.request.urlopen(req)
print(json.loads(resp.read()))
From an encoded config string (e.g. from Outerbounds UI)
from ob_auth import OuterboundsAuth
auth = OuterboundsAuth()
auth.init(config_string="awssm-arn:BASE64...")
headers = auth.api_headers() # {"x-api-key": "..."}
From a service principal (CI/CD, GitHub Actions)
from ob_auth import OuterboundsAuth
auth = OuterboundsAuth()
auth.init_from_service_principal(
service_principal_name="my-cicd-bot",
deployment_domain="my-company.outerbounds.xyz",
github_actions=True, # or jwt_token="..." for static tokens
)
headers = auth.api_headers()
With ob-events
If you also use ob-events, you can share a single auth instance:
from ob_auth import OuterboundsAuth
from ob_events import EventTrigger
auth = OuterboundsAuth()
auth.init_from_config()
# Use auth for direct API calls
headers = auth.api_headers()
# And pass it to EventTrigger
et = EventTrigger(auth=auth)
et.trigger("my_event", {"key": "value"})
Metadata
Release files for ob-auth 0.2.0
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 | |
|---|---|---|---|---|
| ob_auth-0.2.0.tar.gz | 10.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ob_auth-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.5 kB
Release files / ob_auth-0.2.0.tar.gz
| Download URL | ob_auth-0.2.0.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb0953ec21241102e8dd2e4f67fc56e327be67616cf64b7b51b83b54d50a8e65
|
|
BLAKE2b-256 checksum How to use checksums |
728f100bba2f792a0b796c80b186854c578f1fc7e015140519dbef10629a0b54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 26, 2026.
Transparency logRelease files / ob_auth-0.2.0-py3-none-any.whl
| Download URL | ob_auth-0.2.0-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de5ee4d445d73e96e5d28cdf2a43571fa28853dddb6d5cd0d20dd2f6b38616d0
|
|
BLAKE2b-256 checksum How to use checksums |
900938452d7474f6d257634ae567e6229b1382061a233d080d048c004a8a377d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 26, 2026.
Transparency logSecurity for ob-auth 0.2.0
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ob_auth-0.2.0.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 Mar 26, 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.