Configure metadata-generation models end to end #5

New Issue

2026-08-28T13:34:07Z

mptyl commented

2026-08-28 13:34:07 +00:00

Parent

What to build

Allow an installation operator to configure the models available specifically for Description Generation, and allow a Catalog Administrator to see the safe choices in Database Management with the configured default selected. When no usable model exists, the UI must explain why generation is unavailable.

Acceptance criteria

Installation setup YAML accepts a metadata-generation section with unique stable identifiers, display labels, LiteLLM provider/model settings, optional endpoint settings, one default, and an environment-secret reference per model.
Setup validation rejects duplicate identifiers, an unknown or missing default for a non-empty list, malformed model settings, missing secret references, and unusable configured secrets with actionable errors.
Metadata-generation setup remains independent of Pi settings and workspace llm_policy.
The backend exposes only safe model identifiers, labels, and the default; credentials and provider internals never reach the browser.
Database Management selects the configured default and shows a clear disabled state when the safe model list is empty.
Direct API attempts using an unknown or unavailable model are rejected.
Changes take effect after application restart; no hot-reload mechanism is added.
Backend configuration/API tests and frontend MSW tests cover valid, invalid, default, and unavailable-model behavior.

Blocked by

None (can start immediately).

## Parent https://git.tylconsulting.it/mptyl/ThothII/issues/4 ## What to build Allow an installation operator to configure the models available specifically for Description Generation, and allow a Catalog Administrator to see the safe choices in Database Management with the configured default selected. When no usable model exists, the UI must explain why generation is unavailable. ## Acceptance criteria - [ ] Installation setup YAML accepts a metadata-generation section with unique stable identifiers, display labels, LiteLLM provider/model settings, optional endpoint settings, one default, and an environment-secret reference per model. - [ ] Setup validation rejects duplicate identifiers, an unknown or missing default for a non-empty list, malformed model settings, missing secret references, and unusable configured secrets with actionable errors. - [ ] Metadata-generation setup remains independent of Pi settings and workspace llm_policy. - [ ] The backend exposes only safe model identifiers, labels, and the default; credentials and provider internals never reach the browser. - [ ] Database Management selects the configured default and shows a clear disabled state when the safe model list is empty. - [ ] Direct API attempts using an unknown or unavailable model are rejected. - [ ] Changes take effect after application restart; no hot-reload mechanism is added. - [ ] Backend configuration/API tests and frontend MSW tests cover valid, invalid, default, and unavailable-model behavior. ## Blocked by None (can start immediately).

mptyl added the enhancement ready-for-agent labels 2026-08-28 13:34:07 +00:00

mptyl referenced this issue

2026-08-28 13:34:13 +00:00

Generate one selected Catalog Column asynchronously #7

mptyl added a new dependency 2026-08-28 13:34:54 +00:00

#7 Generate one selected Catalog Column asynchronously

mptyl closed this issue

2026-08-28 14:21:10 +00:00

Sign in to join this conversation.