qualis-roku 0.6.2

Lightweight Python client for the Qualis Desk Roku machine API (connect, validate users, clear transactions).

qualis-roku

Python 3.9+ helper for automating Roku Developer Portal workflows when your organization exposes a compatible Qualis Desk–style HTTP API (portal sign-in, test-user validation, clearing channel transactions from CI or tooling).

Install

pip install qualis-roku

From source (development):

pip install -e "./packages/qualis_roku"

Use cases

• Pre-flight checks — Confirm a QA email resolves to a portal test user for a given product (slug from your deployment) before a test run.
• Clean slate — Void test-user purchases / entitlements on a channel before functional or billing-related tests.
• Pipelines — Drive the same flows from Jenkins, GitHub Actions, or internal runners without opening the browser UI.
• Batch operations — Loop over emails or products using the simple (success, message) API.

Design

• connect() — Start (or queue) server-side portal sign-in; no required arguments if your deployment defines default apps via configuration.
• validate(email, product) — Resolve the email in the current portal context for that product slug.
• clear_txn(email, product) — Clear transactions for that email and product.

Each returns (True, message) or (False, message) so callers can branch without exceptions for normal failures.

Lower-level methods (validate_users, clear_transactions, connect_and_wait, …) return full JSON envelopes when you need structured details.

Quick start

Credentials and host can come from environment variables (recommended—nothing secret in code) or be passed explicitly to the constructor. Your internal runbook names the exact variables; typical names look like a “Qualis base URL” and an “API credential” for your deployment.

From environment (set vars in the shell, CI secrets, or .env loaded by your app—do not commit secrets). connect() with no arguments uses default product slugs built into the library unless you override with QUALIS_ROKU_BRANDS / ROKU_BRANDS.

from qualis_roku import QualisRokuClient

# Uses deployment-specific env vars when base_url / api_token are omitted.
with QualisRokuClient() as client:
    ok, msg = client.connect()
    if not ok:
        raise SystemExit(msg)
    ok_v, msg_v = client.validate("[e-mail]", "your-product-slug")
    if not ok_v:
        raise SystemExit(msg_v)
    ok_c, msg_c = client.clear_txn("[e-mail]", "your-product-slug")
    if not ok_c:
        raise SystemExit(msg_c)

Explicit arguments (useful for tests or when config is not on the process environment):

with QualisRokuClient(
    base_url="https://your-qualis-host.example/qualis-desk",
    api_token="your-credential",
) as client:
    ok, msg = client.connect()
    ...

Minimal usage only needs base URL, API token, and checking (ok, message). Optional: QualisRokuClient.try_create() returns (client, err) so the constructor never raises; connect / validate / clear_txn turn failures into (False, message) (not exceptions) for normal errors.

Command line

After install, the qualis-roku executable (or python -m qualis_roku) exposes the same flows without writing Python:

qualis-roku --help
qualis-roku connect
qualis-roku validate [e-mail] your-product-slug
qualis-roku clear [e-mail] your-product-slug
qualis-roku run [e-mail] your-product-slug

Pass --base-url and --api-token or configure the environment variables described in your internal runbook. connect uses built-in default brands unless QUALIS_ROKU_BRANDS / ROKU_BRANDS is set. connect can write a small session file (default ./.qualis_roku_session) so validate / clear can reuse the session; use --print-session-id-only for scripting.

Transient HTTP errors (429, 502–504) and retryable network failures are retried automatically with backoff.

Set QUALIS_ROKU_DEBUG=1 (or pass debug=True to QualisRokuClient) for verbose debug logs on stderr.

Requirements

• Network: HTTPS access from the machine running the client to your Qualis deployment.
• httpx (declared as a dependency).

Documentation

• Full reference (operators + integrators): after install from source or a checkout, open docs/DOCUMENTATION.md — complete env var list, API surface, CLI flags, retries, debug logging, and troubleshooting.
• Your organization may also maintain internal runbooks and HTTP samples for the server API; the PyPI page shows only this README.

Security (general)

• Prefer TLS end-to-end.
• Keep credentials out of source control and logs; use your platform’s secret management.

License

MIT.