Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

config diff reports api.enabled = true after config push disables the Data API (pg_pgrst_no_exposed_schemas)

Cerrado
  • ¿Algo no está bien?
#6,932 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@7ttp ya está trabajando en esto.

Desde el 1/10/2026.

  • #6949 de @7ttp — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

🐛 Bug supabase/cli
Describe the bug

After supabase config push turns the Data API off ([api] enabled = false), supabase config diff still reports api.enabled as true on the remote. config diff --exit-code therefore never exits 0 for a project with the Data API disabled, and every later config push re-sends the same db_schema update.

The push itself works: PATCH /v1/projects/{ref}/postgrest with db_schema: "" is accepted, and GET /v1/projects/{ref}/postgrest then returns "db_schema": "". The effective config (GET /v2/projects/{ref}/config), which config diff reads, returns "db_schema": "pg_pgrst_no_exposed_schemas". That value is the platform's "Data API disabled" marker, per the troubleshooting guide "schema pg_pgrst_no_exposed_schemas does not exist".

The api.enabled row in packages/config/src/project-config/registry.ts (v2.117.0, unchanged in v2.119.0) maps it as:

configPath: ["api", "enabled"],
apiPath: apiDbSchemaPath,
transform: (value) => expectString(value, apiDbSchemaPath).length > 0,

So the marker reads as "enabled".

To reproduce
  1. config.toml with [api] enabled = false.
  2. supabase config push --project-ref <ref> --yes: reports api.enabled [update] local: false, remote: true and updates the API service.
  3. supabase config diff --project-ref <ref> --exit-code: still lists api.enabled (local false, remote true) and exits non-zero.
  4. Steps 2 and 3 repeat identically on every run.
Expected behavior

db_schema == "pg_pgrst_no_exposed_schemas" (as well as "") maps to api.enabled = false, so the diff is clean after a successful disable, and push does not re-send it.

Versions
  • Supabase CLI 2.117.0 (also checked the source of 2.119.0); hosted projects
Related, smaller

config push reports auth.sms.twilio.enabled as unencodable ("cannot turn the active provider off"). Hosted projects start with sms_provider: "twilio" even with phone sign-in off. PATCH /v1/projects/{ref}/config/auth {"sms_provider": null} returns 200 but the value stays "twilio", so a config with no SMS provider can never diff clean. Treating the provider as inactive while external_phone_enabled is false would resolve it.

Lenguaje dominante
TypeScript
Estrellas
2.4k
Forks
533
Merge medio
22 h 20 min
PR fusionados (30 d)
370

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de supabase/cli

Todos los issues de supabase/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.