yungle246 be6612f454 feat: allow knowledge base API keys to be scoped to a single dataset ... Reintroduce the nullable api_tokens.dataset_id column (dropped in 2e9819ca5b28) so dataset API keys can opt into per-knowledge-base scoping: - NULL dataset_id keeps today's workspace-wide behavior, so every existing key and the existing /datasets/api-keys create route are unchanged. - validate_dataset_token rejects a bound key for any other dataset, and for endpoints that carry no dataset id (e.g. list-all), with 403. - CachedApiToken carries dataset_id with a None default so cache entries written before deploy keep deserializing. - The per-dataset console routes in apikey.py (previously dead code that 500ed on a missing ApiToken.dataset_id) now create bound keys; their list returns bound keys plus workspace keys so the dataset page shows the full access picture. - Frontend: the knowledge base API access popover gains an API keys entry; the secret key modal accepts datasetId, shows a scope column, and offers a workspace / this-knowledge-base scope choice on create. New strings are localized for all 23 locales.		2026-06-11 11:41:47 +09:00
..
app	feat: support custom trace session id for Phoenix tracing (#37056)	2026-06-04 08:42:03 +00:00
dataset	refactor(api): migrate console/service_api.dataset.document to BaseModel (#36506)	2026-05-30 14:38:27 +00:00
end_user	chore(api): annotate simple contract responses (#36331)	2026-05-19 06:13:20 +00:00
workspace	chore: reorg imports (#35308)	2026-04-16 08:50:02 +00:00
__init__.py	feat: add service api of HITL (#32826)	2026-04-24 06:37:10 +00:00
index.py	fix(ci): bad pyinfra type coverage report comments (#36482)	2026-05-21 12:08:24 +00:00
wraps.py	feat: allow knowledge base API keys to be scoped to a single dataset	2026-06-11 11:41:47 +09:00