heavy-duty/cast
7
0
Fork 0
Code Issues 4 Pull requests Projects Releases 3 Packages Wiki Activity Actions

fix: restore-db.sh takes the target database name #4

Merged
dan-claude-bot merged 1 commit from fix/restore-db-target-db into main 2026-07-12 09:09:14 +00:00
Conversation 0 Commits 1 Files changed 1 +5 -5
dan-claude-bot commented 2026-07-11 20:25:17 +00:00 (Migrated from github.com)
Copy link

Summary

restore-db.sh piped into psql -U postgres with no -d, so unless the app database is literally named postgres, restored objects land in the maintenance DB. This was flagged as finding #6 in the incubator prod-migration plan's final review, with the fix owed before the Task 9 restore drill.

  • Fourth required argument <db-name>, passed as -d (the error hint shows the psql -lqt command that lists candidates)
  • -v ON_ERROR_STOP=1 so a mid-stream failure aborts the restore instead of continuing silently
  • Confirmation prompt now names the target database as well

Call sites (incubator runbooks restore-drill.md / prod-migration.md) gain the fourth argument — infra-repo doc patch prepared separately.

🤖 Generated with Claude Code

## Summary `restore-db.sh` piped into `psql -U postgres` with no `-d`, so unless the app database is literally named `postgres`, restored objects land in the maintenance DB. This was flagged as finding #6 in the incubator prod-migration plan's final review, with the fix owed before the Task 9 restore drill. - Fourth **required** argument `<db-name>`, passed as `-d` (the error hint shows the `psql -lqt` command that lists candidates) - `-v ON_ERROR_STOP=1` so a mid-stream failure aborts the restore instead of continuing silently - Confirmation prompt now names the target database as well Call sites (incubator runbooks `restore-drill.md` / `prod-migration.md`) gain the fourth argument — infra-repo doc patch prepared separately. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
blocked

Waiting on another PR or issue to land first

  
blocker:ci-red

A check is failing — the agent owes a fix (not a rebase)

  
blocker:conflict

Does not merge — the branch conflicts and the agent owes a rebase

  
blocker:drill-pending

Release ceremony is correct but has no drill record yet

  
blocker:unrequested

Somebody still owes a verdict and nobody was asked for one

  
bug

Something isn't working

  
claimed

a builder owns it: assignee set, a draft PR expected shortly

  
documentation

Improvements or additions to documentation

  
enhancement

New feature or request

  
epic

organizes other issues via a dependency-ordered task list; builders never pick an epic

  
merge-next

Head of the merge queue — merge this one next (set by hand/agent, cleared here)

  
needs-triage

did not come through triage — owes normalization or conversion back

  
ready

triaged, spec complete, unblocked — a builder can start now and succeed

  
release

Release flow and version/packaging work

  
scope:apply

apply/diff/destroy — reconciling onto Coolify

  
scope:capture

draft/capture — reading the live world into a manifest

  
scope:coolify-api

coolify.ts + OpenAPI reference — the client

  
scope:fleet

fleet/inventory/server — placement

  
scope:manifest

manifest/resolve/envtemplate — the manifest language

  
scope:secrets

secrets, age, the encrypted state repo

  
stale

No activity for 48h — needs a poke (sweep-managed)

  
state:addressing

All bots reviewed — coding agent owes the single reply + fixes

  
state:bots-reviewing

Waiting on the bot reviewers to finish the round

  
state:building

PR is a draft — the coding agent is still building

  
state:needs-human

No blockers, all bots approve — waiting on the human reviewer

No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:apply
scope:capture
scope:coolify-api
scope:fleet
scope:manifest
scope:secrets
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/cast#4
No description provided.
Delete branch "fix/restore-db-target-db"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?