fix(BA-6922): use the scoped search route shape the convention documents#13035
Closed
jopemachine wants to merge 2 commits into
Closed
fix(BA-6922): use the scoped search route shape the convention documents#13035jopemachine wants to merge 2 commits into
jopemachine wants to merge 2 commits into
Conversation
`POST /scoped-search` matches neither documented form: the current
`/{entity}/{scope_type}/{scope_id}/search` nor the forward
`/{entity}/scoped/search`. `scheduling-history` already ships the latter as
`/kernels/scoped/search`, so follow it.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
size:XS
jopemachine
marked this pull request as draft
July 22, 2026 08:09
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.
📚 Stacked PRs
BA-6922feat: AppConfig fragment search REST v2 API (admin + scoped)BA-6922fix: use the scoped search route shape the convention documents ← you are hereMerge in order, bottom-up. Each PR is based on the one above it, so its diff shows only its own layer.
Related: #12929 (BA-6922)
Summary
POST /v2/app-config-fragments/scoped-searchmatches neither documented route shape:api/rest/v2/AGENTS.md, currentPOST /v2/{entity}/{scope_type}/{scope_id}/searchapi/rest/v2/AGENTS.md, forward directionPOST /v2/{entity}/scoped/searchPOST /v2/app-config-fragments/scoped-searchPOST /v2/app-config-fragments/scoped/searchscheduling-historyalready ships the forward form asPOST /v2/scheduling-history/kernels/scoped/search, so this follows it rather than inventing a third spelling.The route is introduced by #13020 and does not exist on
main, so this is based on that branch.Test plan
openapi.jsonregenerated with./backend.ai mgr api dump-openapi; the delta is the single path string🤖 Generated with Claude Code