supabase / supavisor / 23647210736

79%

Build Type

push

github

Committed by web-flow

Commit Message

feat: add tenant ban/unban API endpoint (#895)

## Summary

- Adds `PATCH /api/tenants/:external_id` for banning and unbanning
tenants. Banned tenants receive a `FATAL` wire-level error (`EBANNED`)
on any new connection attempt.
- Adds `banned_at` / `ban_reason` fields to the `tenants` table via
migration, and a `TenantBannedError` that is checked in
`ClientHandler.Checks` before a connection is established.



https://linear.app/supabase/issue/POOLER-275/support-banning-and-unbanning-tenants-via-http-api


## OAS / CastAndValidate scope

`OpenApiSpex.Plug.CastAndValidate` is scoped to the `:patch` action only
via a conditional plug. `PutApiSpec` is added to the `:api` pipeline so
the spec is available for casting. Extending `CastAndValidate` to the
remaining actions is left as a TODO for a follow-up PR — those actions
currently pass params as string-keyed maps and would require coordinated
changes.



## TODO
- [x] make sure the migration that adds the fields is safe for the
version of Postgres we run on and won't do the full table scan to fill
in NULLs
- [ ] add metric for tracking banned tenants (likely a separate PR)

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: felipe stival <14948182+v0idpwn@users.noreply.github.com>

Coverage Stats

20 of 20 new or added lines in 7 files covered. (100.0%)

116 existing lines in 16 files now uncovered.

2489 of 3155 relevant lines covered (78.89%)

58302.97 hits per line