Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Chiusa
  • Qualcosa non va?
#7,088 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
42/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cli, docker, postgresql, typescript
Ambito
cli, databases, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

📘 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.

Lingua principale
TypeScript
Stelle
2.4k
Fork
533
Merge medio
22h 20m
PR unite (30g)
370

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di supabase/cli

Tutte le issue di supabase/cli

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.