feat: add AI catalog description generation
This commit is contained in:
@@ -9,11 +9,24 @@ chmod 600 deploy/secrets/thothii.secrets
|
||||
```
|
||||
|
||||
The file uses strict `KEY=VALUE` lines (comments and blank lines are allowed). The supported
|
||||
keys are `THT_MODEL_API_KEY`, `THT_DWH_API_KEY`, `THT_CA`, `THT_SSL_CA`,
|
||||
`THT_OIDC_CLIENT_SECRET`, and `THT_AUTHENTIK_API_TOKEN`. The two authentication keys are fixed
|
||||
empty entries for local authentication and must be populated only in a protected OIDC installation.
|
||||
Other configured values must be non-empty and contain no whitespace. Do not put secrets
|
||||
in the root `.env`, workspace YAML, URLs, logs, or rendered Compose output.
|
||||
installation keys are `THT_MODEL_API_KEY`, `THT_DWH_API_KEY`, `THT_CA`, `THT_SSL_CA`,
|
||||
`THT_OIDC_CLIENT_SECRET`, and `THT_AUTHENTIK_API_TOKEN`. Metadata-generation models may reference
|
||||
exactly one of `THT_METADATA_API_KEY`, `ANTHROPIC_API_KEY`, `AZURE_API_KEY`, `GEMINI_API_KEY`,
|
||||
`DEEPSEEK_API_KEY`, `OPENAI_API_KEY`, `OPENROUTER_API_KEY`, or `ZAI_API_KEY` through their
|
||||
descriptor `apiKeyEnv`. An entry for an explicitly configured endpoint that accepts unauthenticated
|
||||
requests may omit `apiKeyEnv`; hosted/default endpoints must always reference a key.
|
||||
OpenAI-compatible Qwen endpoints that emit reasoning in `content` can additionally set
|
||||
`litellm.disableThinking: true`; the adapter sends the server's bounded chat-template flag so the
|
||||
strict JSON result remains parseable.
|
||||
The two authentication keys must be omitted until they have non-empty values in a protected OIDC
|
||||
installation. Other configured values must be non-empty and contain no
|
||||
whitespace. Do not put secrets in the root `.env`, installation YAML, workspace YAML, URLs, logs,
|
||||
or rendered Compose output.
|
||||
|
||||
`THT_MODEL_API_KEY` remains the generic Pi child credential. Metadata generation is a separate
|
||||
backend-owned runtime and reads only the key named by its own `metadataGeneration.models[].apiKeyEnv`
|
||||
(when present);
|
||||
it does not read Pi settings, `PI_AUTH_FILE`, or workspace `llm_policy`.
|
||||
|
||||
Do not add vector or embedding endpoint credentials to the bundle. Active operator manuals use
|
||||
internal Qdrant and Ollama services, so vector/embedding runtime endpoint secrets are not part of
|
||||
|
||||
Reference in New Issue
Block a user