Repository navigation
feat(secrets): move LLM API Keys into the Secrets menu (#10488) - #10568
Merged
Merged
Conversation
Relocate the standalone /admin/llm-keys admin view into the user app's Secrets section as a child route (/secrets/llm-keys). Add a sub-nav tab bar in SecretsView so users switch between Secrets and LLM API Keys. - Move views/LLMApiKeysView.vue -> views/secrets/LlmApiKeysView.vue - Add child route 'secrets-llm-keys' under /secrets; keep secrets-manager at '' - Add tab bar (router-link) in SecretsView using design tokens - Remove standalone /admin/llm-keys route + nav.llmApiKeys adminMenuItem - Add views.secrets.tabsLabel i18n key across all locales - Keep all issue/list/revoke/rotate functionality + API calls unchanged Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
✅ SSOT Configuration Compliance: Passing🎉 No hardcoded values detected that have SSOT config equivalents! |
Closed
10 tasks done
20 tasks
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
1 participant
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.
Thinking Path
Per operator: credentials belong in the Secrets menu ('this is where we store all our secrets'). LLM API keys were a standalone
/admin/llm-keyspage — moved them under/secretswhere secrets live.What Changed (autobot-frontend only)
views/LLMApiKeysView.vue→views/secrets/LlmApiKeysView.vue(issue/list/revoke/rotate logic +/api/llm-keys/*calls unchanged)./secrets/llm-keys(namesecrets-llm-keys, admin-gated) under the existing/secretslayout.SecretsView.vue(Secrets Manager · LLM API Keys), using design tokens; the LLM Keys tab is admin-gated (v-if="userStore.isAdmin") since the route + backend are admin-only./admin/llm-keysroute +nav.llmApiKeysnavItem (credentials no longer a top-level admin link). i18n keys retained./secretsis reached via the profile dropdown (nav.secrets); the new tab sits within it.Verification (local)
vue-tsc --noEmit→ 0 errors;eslint(changed files) → 0 errors;nav-items-coverage→ 9 passed;vite build→ ✓.Model Used
Opus 4.8
Related #10488 · #10503