unitysvc-data 0.1.9__tar.gz → 0.1.10__tar.gz

{unitysvc_data-0.1.9/src/unitysvc_data.egg-info → unitysvc_data-0.1.10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: unitysvc-data
-Version: 0.1.9
+Version: 0.1.10
 Summary: Standard examples and presets for UnitySVC data packages
 Author-email: Bo Peng <bo.peng@unitysvc.com>
 Maintainer-email: Bo Peng <bo.peng@unitysvc.com>

{unitysvc_data-0.1.9 → unitysvc_data-0.1.10}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "unitysvc-data"
-version = "0.1.9"
+version = "0.1.10"
 description = "Standard examples and presets for UnitySVC data packages"
 readme = "README.md"
 authors = [{ name = "Bo Peng", email = "bo.peng@unitysvc.com" }]

{unitysvc_data-0.1.9 → unitysvc_data-0.1.10}/src/unitysvc_data/_manifest.json

@@ -45,6 +45,8 @@
     "llm_code_example_vision_javascript": "llm_code_example_vision_javascript_v1",
     "llm_code_example_vision_requests": "llm_code_example_vision_requests_v1",
     "llm_code_example_vision_shell": "llm_code_example_vision_shell_v1",
+    "llm_connectivity": "llm_connectivity_v1",
+    "llm_connectivity_anthropic": "llm_connectivity_anthropic_v1",
     "llm_description": "llm_description_v1",
     "llm_request_template": "llm_request_template_v1",
     "notification_description": "notification_description_v1",
@@ -52,6 +54,7 @@
     "s3_code_example": "s3_code_example_v1",
     "s3_connectivity": "s3_connectivity_v1",
     "s3_description": "s3_description_v1",
+    "smtp_code_example": "smtp_code_example_v1",
     "smtp_connectivity": "smtp_connectivity_v2",
     "uptime_description": "uptime_description_v1"
   },
@@ -677,6 +680,34 @@
       "source_readme": "llm/code-example-vision-shell/README.md",
       "version": 1
     },
+    "llm_connectivity_anthropic_v1": {
+      "category": "connectivity_test",
+      "description": "Verify an Anthropic-Messages-API LLM endpoint by issuing a tiny one-token message",
+      "example_file": "llm/connectivity-anthropic/connectivity-v1.sh.j2",
+      "is_active": true,
+      "is_public": false,
+      "meta": {
+        "output_contains": "connectivity ok"
+      },
+      "mime_type": "bash",
+      "preset_name": "llm_connectivity_anthropic",
+      "source_readme": "llm/connectivity-anthropic/README.md",
+      "version": 1
+    },
+    "llm_connectivity_v1": {
+      "category": "connectivity_test",
+      "description": "Verify an OpenAI-compatible LLM endpoint by issuing a tiny chat completion",
+      "example_file": "llm/connectivity/connectivity-v1.sh.j2",
+      "is_active": true,
+      "is_public": false,
+      "meta": {
+        "output_contains": "connectivity ok"
+      },
+      "mime_type": "bash",
+      "preset_name": "llm_connectivity",
+      "source_readme": "llm/connectivity/README.md",
+      "version": 1
+    },
     "llm_description_v1": {
       "category": "getting_started",
       "description": "Customer-facing overview of an OpenAI-compatible LLM gateway service",
@@ -771,6 +802,20 @@
       "source_readme": "s3/description/README.md",
       "version": 1
     },
+    "smtp_code_example_v1": {
+      "category": "code_example",
+      "description": "Python example: send a test email via the UnitySVC SMTP gateway",
+      "example_file": "smtp/code-example/code-example-v1.py.j2",
+      "is_active": true,
+      "is_public": true,
+      "meta": {
+        "output_contains": "connectivity ok"
+      },
+      "mime_type": "python",
+      "preset_name": "smtp_code_example",
+      "source_readme": "smtp/code-example/README.md",
+      "version": 1
+    },
     "smtp_connectivity_v1": {
       "category": "connectivity_test",
       "description": "Verify SMTP server returns a 220 greeting on connect",

unitysvc_data-0.1.10/src/unitysvc_data/examples/llm/connectivity/README.md

@@ -0,0 +1,46 @@
++++
+preset_name = "llm_connectivity"
+category = "connectivity_test"
+mime_type = "bash"
+file = "connectivity.sh.j2"
+description = "Verify an OpenAI-compatible LLM endpoint by issuing a tiny chat completion"
+is_active = true
+is_public = false
+meta = { output_contains = "connectivity ok" }
++++
+
+# llm / connectivity — chat completion smoke test
+
+Connectivity check for OpenAI-compatible LLM services routed through
+the UnitySVC LLM gateway. Posts a one-token chat completion against
+`{{ routing_key.model }}`, asserts the gateway returned a real
+`choices` array, and prints `connectivity ok` on success.
+
+This is a step deeper than `api_connectivity` (which just checks the
+URL responds). For an LLM service, "is the gateway alive?" is too
+weak — what we actually want to know is "can this model produce a
+completion?" The cheap one-token request answers that without
+generating a real reply.
+
+## Template variables (filled in by the platform when rendering for a given access interface)
+
+- `{{ service_base_url }}` — endpoint base URL.
+- `{{ routing_key.model }}` — model id.
+
+## Environment variables (read at runtime)
+
+- `UNITYSVC_API_KEY` — required. Bearer token: customer's svcpass for
+  gateway access, or an upstream key when wired as a secret (BYOK).
+
+## Versions
+
+### v1 — initial release
+
+- POST `/chat/completions` with `messages: [{role: user, content: "ping"}]` and `max_tokens: 1`.
+- `curl --fail-with-body` so 4xx / 5xx surface as non-zero exit + body in stderr.
+- `grep -q '"choices"'` so a 200 with an unrelated body (rare, but
+  some upstream errors return 200 with an `{"error": ...}` envelope)
+  still fails.
+- Output contains `connectivity ok` — paired with the
+  `output_contains = "connectivity ok"` meta so the run-tests flow can
+  confirm a real round-trip.

unitysvc_data-0.1.10/src/unitysvc_data/examples/llm/connectivity/connectivity-v1.sh.j2

@@ -0,0 +1,15 @@
+#!/bin/bash
+# LLM connectivity probe: POST a one-token chat completion against the
+# rendered model and assert the gateway returned a real ``choices``
+# array.  Cheap, non-zero exit on any 4xx / 5xx, prints "connectivity ok"
+# on success so output_contains can verify a real round-trip.
+set -e -o pipefail
+
+: "${UNITYSVC_API_KEY:?UNITYSVC_API_KEY is not set}"
+
+curl --fail-with-body -sS "{{ service_base_url }}/chat/completions" \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer ${UNITYSVC_API_KEY}" \
+  -d '{"model":"{{ routing_key.model }}","messages":[{"role":"user","content":"ping"}],"max_tokens":1}' \
+  | grep -q '"choices"'
+echo "connectivity ok"

unitysvc_data-0.1.10/src/unitysvc_data/examples/llm/connectivity-anthropic/README.md

@@ -0,0 +1,57 @@
++++
+preset_name = "llm_connectivity_anthropic"
+category = "connectivity_test"
+mime_type = "bash"
+file = "connectivity.sh.j2"
+description = "Verify an Anthropic-Messages-API LLM endpoint by issuing a tiny one-token message"
+is_active = true
+is_public = false
+meta = { output_contains = "connectivity ok" }
++++
+
+# llm / connectivity-anthropic — Anthropic Messages API smoke test
+
+Connectivity check for Anthropic-Messages-API LLM services
+(`/v1/messages`, primarily Claude-family models). Companion to
+`llm_connectivity` (OpenAI-compatible `/chat/completions`) — Anthropic's
+API isn't OpenAI-shaped (different endpoint, required `max_tokens`,
+top-level `system`, `content[].text` response), so it needs its own
+preset.
+
+## Differences vs `llm_connectivity`
+
+| | `llm_connectivity` | `llm_connectivity_anthropic` |
+|---|---|---|
+| Endpoint | `/chat/completions` | `/v1/messages` |
+| Auth header | `Authorization: Bearer …` | `x-api-key: …` |
+| Required header | — | `anthropic-version: 2023-06-01` |
+| Required body fields | `model`, `messages` | `model`, `messages`, `max_tokens` |
+| Response shape | `"choices"` | `"content"` |
+
+## Template variables (filled in by the platform when rendering for a given access interface)
+
+- `{{ service_base_url }}` — endpoint base URL.
+- `{{ routing_key.model }}` — model id.
+
+## Environment variables (read at runtime)
+
+- `UNITYSVC_API_KEY` — required. Sent as the `x-api-key` header.
+  Customer's svcpass for gateway access, or an upstream key when
+  wired as a secret (BYOK).
+
+## Versions
+
+### v1 — initial release
+
+- POST `/v1/messages` with `messages: [{role: user, content: "ping"}]`
+  and `max_tokens: 1`.
+- Sends `anthropic-version: 2023-06-01` (the version pinned by the
+  current Python SDK; matches what gateways and Claude apps expect).
+- `curl --fail-with-body` so 4xx / 5xx exit non-zero with the body
+  on stderr.
+- `grep -q '"content"'` — Anthropic returns the assistant text in a
+  `content` array, so this confirms a real response envelope rather
+  than a 200 with an unrelated body.
+- Output contains `connectivity ok` — paired with the
+  `output_contains = "connectivity ok"` meta so the run-tests flow
+  can confirm a real round-trip.

unitysvc_data-0.1.10/src/unitysvc_data/examples/llm/connectivity-anthropic/connectivity-v1.sh.j2

@@ -0,0 +1,16 @@
+#!/bin/bash
+# Anthropic Messages API connectivity probe: POST a one-token message
+# against the rendered model and assert the gateway returned a real
+# ``content`` array.  Cheap, non-zero exit on any 4xx/5xx, prints
+# "connectivity ok" on success.
+set -e -o pipefail
+
+: "${UNITYSVC_API_KEY:?UNITYSVC_API_KEY is not set}"
+
+curl --fail-with-body -sS "{{ service_base_url }}/v1/messages" \
+  -H "Content-Type: application/json" \
+  -H "x-api-key: ${UNITYSVC_API_KEY}" \
+  -H "anthropic-version: 2023-06-01" \
+  -d '{"model":"{{ routing_key.model }}","max_tokens":1,"messages":[{"role":"user","content":"ping"}]}' \
+  | grep -q '"content"'
+echo "connectivity ok"

unitysvc_data-0.1.10/src/unitysvc_data/examples/smtp/code-example/README.md

@@ -0,0 +1,64 @@
++++
+preset_name = "smtp_code_example"
+category = "code_example"
+mime_type = "python"
+file = "code-example.py.j2"
+description = "Python example: send a test email via the UnitySVC SMTP gateway"
+is_active = true
+is_public = true
+meta = { output_contains = "connectivity ok" }
++++
+
+# smtp / code-example — send-email smoke test
+
+Customer-facing Python example for SMTP services routed through the
+UnitySVC gateway (BYOK relay, multi-enrollment relay, mailpit-backed
+test gateway). Composes a one-line text email and sends it, picking
+implicit TLS (SMTPS) vs plain-with-STARTTLS based on the rendered URL
+or the seller's `tls` flag.
+
+The same template covers both render modes — local-testing
+(`local_testing == True`) inlines the seller's upstream credentials
+for ops-test runs, gateway mode parses `service_base_url` and reads
+the customer's API key from `UNITYSVC_API_KEY`.
+
+## Template variables
+
+**Local-testing mode** (`{% raw %}{% if local_testing %}{% endraw %}`) — the renderer fills these
+from the offering's `upstream_access_config` after substituting
+`ops_testing_parameters`:
+
+- `{% raw %}{{ host }}{% endraw %}` — upstream SMTP host.
+- `{% raw %}{{ port }}{% endraw %}` — upstream SMTP port. Defaults to 587 (submission).
+- `{% raw %}{{ tls }}{% endraw %}` — `true` ⇒ implicit TLS (port 465 / SMTPS),
+  `false` ⇒ plain TCP with optional STARTTLS upgrade. Accepted as
+  Python bool, lowercase string, or capitalised string.
+- `{% raw %}{{ username }}{% endraw %}`, `{% raw %}{{ password }}{% endraw %}` — upstream credentials. Inlining
+  these is fine because this branch is only ever rendered for the
+  seller's own ops-test flow; customers never see local-testing
+  output.
+
+**Gateway mode** (the `else` branch) — the renderer fills these from
+the listing's access interface:
+
+- `{% raw %}{{ service_base_url }}{% endraw %}` — `smtp://host:port` or
+  `smtps://host:port`.
+- `{% raw %}{{ routing_key.username }}{% endraw %}` — SMTP username (per the listing's
+  `routing_key`).
+
+## Environment variables (read at runtime)
+
+- `UNITYSVC_API_KEY` — gateway-mode SMTP password. Always pulled from
+  env, never inlined into rendered output (per-customer secret).
+
+## Versions
+
+### v1 — initial release
+
+- Implicit TLS via `smtplib.SMTP_SSL` when `use_ssl`; otherwise plain
+  `smtplib.SMTP` with optional STARTTLS upgrade detected via
+  `server.has_extn("STARTTLS")`.
+- 10-second connect/operation timeout.
+- Prints `connectivity ok` on success — paired with the
+  `output_contains = "connectivity ok"` meta so the platform's
+  run-tests flow can verify a real send completed.

unitysvc_data-0.1.10/src/unitysvc_data/examples/smtp/code-example/code-example-v1.py.j2

@@ -0,0 +1,46 @@
+import smtplib
+from email.mime.text import MIMEText
+
+{% if local_testing %}
+# Seller ops-testing mode. The renderer inlines upstream host/port/credentials
+# from the offering's upstream_access_config (after substituting customer
+# secrets from ops_testing_parameters). The seller only ever sees their own
+# credentials, so inlining them is fine — this branch never reaches a customer.
+smtp_host = "{{ host }}"
+smtp_port = {{ port | default(587) }}
+use_ssl = "{{ tls | default(false) }}".lower() == "true"
+username = "{{ username | default('') }}"
+password = "{{ password | default('') }}"
+{% else %}
+# Gateway mode (customer-facing). The base URL is rendered inline; username
+# comes from the listing's routing_key. The API key stays as an env-var
+# lookup — keys are never inlined into rendered output, on any code path.
+import os
+from urllib.parse import urlparse
+
+parsed = urlparse("{{ service_base_url }}")
+smtp_host = parsed.hostname
+smtp_port = parsed.port or 587
+use_ssl = parsed.scheme == "smtps"
+username = "{{ routing_key.username }}"
+password = os.environ["UNITYSVC_API_KEY"]
+{% endif %}
+
+msg = MIMEText("Hello from UnitySVC SMTP Gateway!")
+msg["Subject"] = "Test Email via SMTP Gateway"
+msg["From"] = "test@example.com"
+msg["To"] = "recipient@example.com"
+
+# Implicit TLS (port 465 / smtps://) → SMTP_SSL.
+# Plain TCP with optional STARTTLS upgrade (port 587 / smtp://) → SMTP.
+cls = smtplib.SMTP_SSL if use_ssl else smtplib.SMTP
+with cls(smtp_host, smtp_port, timeout=10) as server:
+    if not use_ssl:
+        server.ehlo()
+        if server.has_extn("STARTTLS"):
+            server.starttls()
+            server.ehlo()
+    if username and password:
+        server.login(username, password)
+    server.send_message(msg)
+print("connectivity ok")

{unitysvc_data-0.1.9 → unitysvc_data-0.1.10/src/unitysvc_data.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: unitysvc-data
-Version: 0.1.9
+Version: 0.1.10
 Summary: Standard examples and presets for UnitySVC data packages
 Author-email: Bo Peng <bo.peng@unitysvc.com>
 Maintainer-email: Bo Peng <bo.peng@unitysvc.com>

{unitysvc_data-0.1.9 → unitysvc_data-0.1.10}/src/unitysvc_data.egg-info/SOURCES.txt

@@ -104,6 +104,10 @@ src/unitysvc_data/examples/llm/code-example-vision-requests/README.md
 src/unitysvc_data/examples/llm/code-example-vision-requests/code-example-vision-v1.py.j2
 src/unitysvc_data/examples/llm/code-example-vision-shell/README.md
 src/unitysvc_data/examples/llm/code-example-vision-shell/code-example-vision-v1.sh.j2
+src/unitysvc_data/examples/llm/connectivity/README.md
+src/unitysvc_data/examples/llm/connectivity/connectivity-v1.sh.j2
+src/unitysvc_data/examples/llm/connectivity-anthropic/README.md
+src/unitysvc_data/examples/llm/connectivity-anthropic/connectivity-v1.sh.j2
 src/unitysvc_data/examples/llm/description/README.md
 src/unitysvc_data/examples/llm/description/description-v1.md
 src/unitysvc_data/examples/llm/request-template/README.md
@@ -118,6 +122,8 @@ src/unitysvc_data/examples/s3/connectivity/README.md
 src/unitysvc_data/examples/s3/connectivity/connectivity-v1.py.j2
 src/unitysvc_data/examples/s3/description/README.md
 src/unitysvc_data/examples/s3/description/description-v1.md
+src/unitysvc_data/examples/smtp/code-example/README.md
+src/unitysvc_data/examples/smtp/code-example/code-example-v1.py.j2
 src/unitysvc_data/examples/smtp/connectivity/README.md
 src/unitysvc_data/examples/smtp/connectivity/connectivity-v1.sh.j2
 src/unitysvc_data/examples/smtp/connectivity/connectivity-v2.sh.j2