fix(supabase): db:trial closure review fixes
Strict absent detection (stderr sentence per kind, measured on Docker 29.9.3), tri-state container_running, empty-volume check before restore, quieter DB init and rotation logging, backup/migrate refuse while the app runs, lock first in start/stop, truthful rotate-secrets and post-create checks. Stub reproduces Docker's stdout/stderr split. Harness 364/0.
This commit is contained in:
1 parent
a78da9f4e2
commit
d3bdbbe0ba
5 files changed
+357
-54
No files matched your search
@@ -170,7 +170,7 @@ recreates a missing container; backups check free space, list each archive back
|
||||
backup of what it would remove and names the manual removal commands; the stub harness is run by hand, not by
|
||||
`check:all` (it reads the host's real ports). R13 (owner 2026-11-10): the shared trial dev server serves exactly
|
||||
one of two listed stacks (`apps/app/vite/trial-targets.ts`), and `db-trial.sh` checks each operation's target and
|
||||
every key it hands over (`SUPABASE.md` §5.2). Known limit: `app` takes no lock, so a `stop`, `destroy`, `restore`
|
||||
every key it hands over (`SUPABASE.md` §5.2). Known limit: `app` takes no lock, so a `stop`, `backup`, `migrate`, `destroy`, `restore`
|
||||
or rotation run in another terminal just before Vite listens goes ahead (`SUPABASE.md` §5.2). The tests of §5 that
|
||||
create a stack under a test prefix were not run (owner brief: environment-free checks only); the stub harness
|
||||
replaces them until the first `create`.
|
||||
Reference in new issue
Block a user