Add batch get-by-IDs RPCs to AdminService for users, service users, and projects
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 344
- Forks
- 47
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 26
Description
Problem
AdminService can list entire collections (ListAllUsers, ListAllServiceUsers, ListAllOrganizations), but there's no way to resolve a known set of IDs to entities in a single call. Given a list of IDs, the options today are to issue N single Get calls or to list a whole collection and filter — N round-trips, or over-fetching.
Proposal
Add batch get-by-IDs RPCs to AdminService (superuser-gated, consistent with the existing ListAll* admin RPCs, since these are cross-org lookups that aren't org-scoped):
BatchGetUsers(user_ids: []string) → users: []UserBatchGetServiceUsers(service_user_ids: []string) → service_users: []ServiceUserBatchGetProjects(project_ids: []string) → projects: []Project
Each takes a repeated ID field and returns the matching existing entity messages. A bounded max number of IDs per request (like BatchCheckPermission) would be reasonable.
Notes
- The lookup already exists internally —
GetByIDsis implemented incore/user,core/serviceuser, andcore/group; it just isn't exposed at the API layer. (core/groupcould get aBatchGetGroupstoo if useful.) core/projectwould need a batch lookup added; it currently has only singleGetand a filteredList.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the AdminService definitions and existing ListAllUsers, ListAllServiceUsers, ListAllOrganizations, and BatchCheckPermission RPCs. Read the GetByIDs implementations in core/user, core/serviceuser, and core/group, plus the single Get and filtered List paths in core/project. Done means superuser-gated batch RPCs for users, service users, and projects, with bounded IDs and coverage for matching results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100