Keys + Restormel Testing onboarding

Canonical repo copy: docs/keys-testing-onboarding.md — same operational steps; update that file first, then keep this page aligned.

Goal: Run judge_rubric and Keys-backed resolve from the Testing CLI without hand-rolling env from scattered docs. Use Connections for encrypted hosted provider keys (when the deployment is configured), Gateway keys for RESTORMEL_KEYS_API_TOKEN, and the Restormel Testing dashboard page for RESTORMEL_PROJECT_ID and environment IDs.

Steps (summary)

  1. Sign in to the dashboard.
  2. Connections (/keys/dashboard/integrations): add a provider — paste a hosted API key once (encrypted at rest) or a vault reference only. Never shown in full after save.
  3. Gateway keys (/keys/dashboard/access): create an rk_… key for the Restormel Testing project (or a project you bind to).
  4. Restormel Testing (/keys/dashboard/testing): copy project ID, environment IDs, and the env snippet pattern.
  5. Run pnpm exec testing doctor locally; it checks Keys URL/token and reminds you if RESTORMEL_PROJECT_ID is missing when the Keys base URL is set.

Related