Wire platform-managed LLM defaults into workspaces #1815
Reference in New Issue
Block a user
Delete Branch "fix/platform-managed-llm-default"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Consumes the controlplane platform-managed LLM tenant config in workspace-server provisioning.\n\nWhat changed:\n- RefreshEnvFromCP continues to apply CP-provided LLM config values.\n- prepareProvisionContext now injects platform-managed LLM env before runtime model env.\n- When org mode is platform_managed and no workspace OPENAI_API_KEY exists, workspace env gets OPENAI_BASE_URL + OPENAI_API_KEY pointed at the CP OpenAI-compatible proxy using the tenant token.\n- If the user/workspace already set OPENAI_API_KEY, it is preserved.\n- Missing selected model defaults through MOLECULE_LLM_DEFAULT_MODEL from CP config, keeping tenant code out of model-catalog ownership.\n\nVerification:\n- go test ./... from workspace-server\n- git diff --check\n\nDependency/blocker:\n- Depends on molecule-controlplane PR #275 being deployed.\n- Deployment remains blocked until LLM provider keys/default model are populated in operator SSOT, because PR #275 enforces SSOT sync.
Cross-author LGTM — clean implementation.
Status update from implementation pass:
Update: the previous SSOT blocker is resolved. LLM keys/default model are now in Infisical at /shared/controlplane/llm, mirrored to the CP-only operator runtime cache /etc/molecule-bootstrap/controlplane-llm.env, and synced into Railway staging + production. Remaining gates are CI completion on controlplane after the script update, then normal merge/deploy verification.
LGTM — platform-managed LLM defaults wired into workspaces.