Add SCIM discovery routes

Ricardo Amarillarequested to merge
452118-scim-discovery-schemas-routes into main

What does this MR do and why?

Paired HTTP Router MR for the SCIM discovery endpoints stack in gitlab-org/gitlab (RFC 7644 §4, gitlab-org/gitlab#452118). It covers the routes of all three GitLab MRs at once, so the router only needs one update:

GitLab MR Routes
gitlab-org/gitlab!257947 (merged) /api/scim/:version/{application,groups/:group}/Schemas and .../Schemas/:id
gitlab-org/gitlab!258175 (merged) /api/scim/:version/{application,groups/:group}/ServiceProviderConfig
gitlab-org/gitlab!258176 (merged) /api/scim/:version/{application,groups/:group}/ResourceTypes and .../ResourceTypes/:id

Refreshes test/routes/gitlab_routes.json from the 452118-scim-discovery-4-resource-types branch, the top of the stack (10 added, 0 updated, 13 router-only routes kept), and updates the vitest snapshot. Generated route guards didn't change.

All routes require a SCIM token, so per Adding GitLab routes to the HTTP Router this is case 1: every one of the 40 new snapshot rows matches the existing /api/* rule with a null claim (routed by the token), and no routing change is needed.

⚠️ Merge order

Merge this MR right before gitlab-org/gitlab!257947 (merged), the first GitLab MR that adds these routes. It is set as a blocking dependency of that MR. Right before merging, I'll re-run npm run download-gitlab-routes -- 452118-scim-discovery-4-resource-types in case either side changed.

Because cells-routes:router-in-sync requires the two snapshots to be byte-identical, and this MR already contains the routes of gitlab-org/gitlab!258175 (merged) and gitlab-org/gitlab!258176 (merged), the job will keep failing on gitlab-org/gitlab!257947 (merged) and gitlab-org/gitlab!258175 (merged) even after this merges. Those two MRs will use the pipeline:skip-router-sync label, with the reason stated in their descriptions. gitlab-org/gitlab!258176 (merged), the top of the stack, should pass the check once its snapshot matches the router's. That also depends on the 13 router-only routes kept here (from other teams' pending GitLab MRs) reaching GitLab master first.

References

How to set up and validate locally

  1. npm install
  2. npm run download-gitlab-routes -- 452118-scim-discovery-4-resource-types
  3. npm run generate-route-guards
  4. npm run test -- routes.spec.ts and verify it passes with no snapshot changes.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist.

🤖 Generated with Claude Code

Edited by Ricardo Amarilla

Merge request reports