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

Safe local credential rotation without data loss — CLI v2.120.0

Cerrado
  • ¿Algo no está bien?
#7,088 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
42/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cli, docker, postgresql, typescript
Área
cli, databases, security

Línea de trabajo

Start by reviewing the CLI documentation and the local stack configuration for credential generation and service restart behavior in v2.120.0. Determine whether credentials can be rotated independently while preserving PostgreSQL data and Docker volumes, then document supported verification and rollback steps. Done means the procedure is verified for that version and explains how to reject old credentials safely.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

📘 Docs supabase/cli
Affected area

Auth

Supabase CLI version

v2.120.0

Operating system

Windows 11

Installation method

None

Command
supabase start
Actual output
No CLI error or crash. This report requests guidance for safely rotating potentially compromised local credentials.
Expected behavior

A documented, non-destructive procedure to rotate local privileged credentials while preserving PostgreSQL data and Docker volumes, including verification and rollback instructions.

Steps to reproduce
  1. Run a local development stack using supabase start on CLI v2.120.0. 2. Consider a locally generated privileged credential potentially compromised. 3. Attempt to identify an officially documented non-destructive rotation procedure. 4. No verified procedure has been established for this CLI version.
Crash report ID

No response

Docker and service versions
Additional context

I am looking for an officially supported way to revoke or rotate a potentially compromised local privileged credential in Supabase CLI v2.120.0.

I need to preserve the existing PostgreSQL database and Docker volumes without running supabase db reset, deleting volumes, or recreating the stack destructively.

Could maintainers clarify:

  1. How to identify the type of locally generated credential without printing its value.
  2. Whether privileged API keys and JWT signing keys can be rotated independently.
  3. Whether in-place, non-destructive rotation is supported in v2.120.0.
  4. Which services need restarting and how to verify old credentials are rejected.
  5. Whether a supported CLI upgrade provides a safe alternative if v2.120.0 cannot do this.
  6. How to preserve data and safely roll back if the procedure fails.

No credentials, logs, or project-specific configuration are included for security reasons.

Lenguaje dominante
TypeScript
Estrellas
2.4k
Forks
533
Merge medio
1 d 5 h
PR fusionados (30 d)
338

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.