Safe local credential rotation without data loss — CLI v2.120.0
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 42/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- cli, docker, postgresql, typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 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:
- How to identify the type of locally generated credential without printing its value.
- Whether privileged API keys and JWT signing keys can be rotated independently.
- Whether in-place, non-destructive rotation is supported in v2.120.0.
- Which services need restarting and how to verify old credentials are rejected.
- Whether a supported CLI upgrade provides a safe alternative if v2.120.0 cannot do this.
- How to preserve data and safely roll back if the procedure fails.
No credentials, logs, or project-specific configuration are included for security reasons.
- 主要语言
- TypeScript
- 星标
- 2.4k
- 派生
- 533
- 平均合并
- 22 小时 20 分钟
- 30 天内合并 PR
- 370
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
supabase/cli 的其他 Issue
-
🐛 Bug supabase/cli
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
db schema declarative sync: no way to fail (non-zero exit) when the generated migration is destructive可能重新可做 关联的 PR 已关闭且未合并。 未关闭✨ Feature supabase/cli
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
stack: the HTTP gateway closes idle keep-alive connections after 5 s, so a client whose event loop is blocked gets ECONNRESET (`fetch failed`) on its next request可能已有人在做 @7ttp 于 12 天前认领。 未关闭🐛 Bug supabase/cli
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
📘 Docs supabase/cli
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
🐛 Bug supabase/cli
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
相似的 Issue
-
fix(frontend): correct VITE_IS_DEVELPOMENT typo in shared/app.ts and align dev environment flags未关闭
难度 2/5 1-3 小时 新手友好度 75/100
vicharanashala/ajrasakha#1439 ·
维护者通常 1 天内回复
-
approved check:passed streams:add
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
backnotprop/plannotator#1932 ·
维护者通常 1 天内回复
-
难度 2/5 半天 新手友好度 62/100
ibm-granite/granite.build#504 ·
维护者通常 2 天内回复
-
reproduced
难度 2/5 1-3 小时 新手友好度 82/100
anomalyco/opencode#55676 · 1 条评论 ·
维护者通常 1 天内回复