Repository navigation
feat(ui): remove standalone admin Key pool tab - #33
Merged
Merged
Conversation
Admin no longer needs a separate Key pool management screen: admins configure upstream keys through the same listing form as regular users (provider → plan → model, key, quota, availability window) on the Sharing page — in enterprise use the admin lists keys and employees consume them, which is exactly what a key pool is. Remove the admin "Key 池" tab and its pane (add-key button, keys-body table, revoke handling, KEYS mock); remaining admin tabs: members, usage, org, ops. "Key 池" stays as a data-layer concept (docs/architecture.md 4.2 notes the unified entry). Syncs docs v1.11 (US-12, enterprise flow, alignment table) and ui/README.md. Refs: rant 2026-08-17T10:56:47 (管理视图移除独立"Key 池"管理)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove the standalone admin "Key 池" (Key pool) tab. Admins configure upstream keys through the same listing form as regular users on the Sharing page (provider → plan → model, key, quota, availability window) — in enterprise use, admins list keys and employees consume them, which is exactly what a key pool is. No separate admin Key pool screen needed.
Rant reference
Host instruction (rant
2026-08-17T10:56:47, 管理视图移除独立"Key 池"管理):Changes
ui/index.html: removed the "Key 池" tab button and its pane (ak-search,add-key-btn,keys-bodytable); "成员管理" is now the default admin tab; header subtitle updated. Remaining admin tabs: 成员管理 / 用量报表 / 组织管理 / 平台运营ui/js/app.js: removedKEY_STATUS, thetab === "keys"render branch, and theadd-key-btn/ak-search/keys-bodyrevoke event bindingsui/js/data.js: removed theKEYSmock (SHARINGS is the listing data source)docs/user-stories.md: bumped to v1.11 — US-12 rewritten (admin configures upstream keys via 上架, shared listing = key pool view, no standalone admin screen); enterprise flow step + alignment table updateddocs/architecture.md4.2: "Key 池" stays as a data-layer concept; added note that the management entry is unified via 上架 (no standalone admin UI)ui/README.md: synced admin sectionVerification
KEY_STATUS|ak-search|add-key-btn|data-key-revoke|keys-body|D.KEYS|data-admin-tab="keys"|data-admin-pane="keys"in ui/ → zero matches (remainingak-searchhits are the Settings page's API-key search, a different feature)node --check ui/js/app.js/ui/js/data.jspasscargo testpasses (1 passed)cargo fmt --checkpasses