Configure and verify the model provider #10

Open
opened 2026-07-14 22:32:17 -04:00 by caleb-brown · 0 comments
Owner

What to build

A Temper Operator can configure the Deployment's OpenAI-compatible model provider, verify that it supports Temper's required contract, and understand failures before reviewing live code.

Acceptance criteria

  • An Operator can save one active provider endpoint, model, typed credentials, trust settings, and bounded request defaults.
  • Provider credentials are encrypted, never displayed after entry, and excluded from logs and diagnostic responses.
  • A connection test verifies authentication, timeout behavior, and the structured-output capability Temper requires.
  • Invalid configuration, unreachable endpoints, certificate failures, and incompatible responses produce actionable Operator-facing errors.
  • Private endpoints and custom certificate authorities are supported without forwarding credentials across origins.
  • Contract tests cover a deterministic provider double plus representative success and failure responses.

Blocked by

  • #9 — Boot a secure Temper Deployment
## What to build A Temper Operator can configure the Deployment's OpenAI-compatible model provider, verify that it supports Temper's required contract, and understand failures before reviewing live code. ## Acceptance criteria - [ ] An Operator can save one active provider endpoint, model, typed credentials, trust settings, and bounded request defaults. - [ ] Provider credentials are encrypted, never displayed after entry, and excluded from logs and diagnostic responses. - [ ] A connection test verifies authentication, timeout behavior, and the structured-output capability Temper requires. - [ ] Invalid configuration, unreachable endpoints, certificate failures, and incompatible responses produce actionable Operator-facing errors. - [ ] Private endpoints and custom certificate authorities are supported without forwarding credentials across origins. - [ ] Contract tests cover a deterministic provider double plus representative success and failure responses. ## Blocked by - [#9](https://git.caleb-brown.dev/caleb-brown/temper/issues/9) — Boot a secure Temper Deployment
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#10
No description provided.