Loading
feat(proto): add BulkUpsertClients and UpsertResult
The auth proto now has BulkUpsertClients, which takes 1 to 1,000 UpsertClient records and answers one UpsertResult per record, in input order. The Rails Layer 4 sweep sends one call per row today, and the refresh-token backfill alone is about 46M rows (gitlab-org/gitlab#635781 (closed)).
UpsertResult is the shared per-record outcome of every bulk upsert: a reason enum that is REASON_WRITTEN on success and names the refusal otherwise, and a message. The interceptor checks only the list bound; the handler validates each item, which the next part adds.
Nothing serves the RPC yet, so no behaviour changes.
Part 1 of 7. The full change is in !959 (closed), the integration MR, kept open for the big picture.
- !988 (merged) feat(proto): add BulkUpsertClients and UpsertResult <- this MR
- !989 (merged) feat(auth): add BulkUpsertClients with per-record results
- !990 (merged) refactor(auth): move the bulk record helpers to internal/batch
- !991 (merged) feat(auth): add refresh-token BulkUpsert with per-record results
- !992 (merged) feat(auth): add refresh-token BulkDelete
- !993 (merged) feat(auth): add refresh-token GetState
- !994 (merged) feat(auth): count bulk RPC records by outcome
Next: !989 (merged)
Edited by Shilpa Kundapur