Files
supabase/apps/studio/tests/unit/LogicalBackupCliInstructions.test.ts
Jordi Enric 21584fe512 feat(studio): add backup cli instructions (#44621)
## Problem

When a project is paused, in a failed state, or about to be deleted,
users have no obvious way to take a logical backup of their data before
proceeding. This is particularly risky at deletion time — once deleted,
data is gone.

## Solution

Introduce a new `LogicalBackupCliInstructions` component that surfaces
ready-to-run `supabase db dump` commands pre-filled with the project's
direct connection details.

### Where it appears

| State | How |
|---|---|
| Project paused (restorable) | Inline in `ProjectPausedState` with a
note to resume first |
| Pause failed | Dialog via "Download backup" button when no backup is
available |
| Restore failed | Dialog via "Download backup" button when no backup is
available |
| Delete project modal | Inline in `DeleteProjectModal` for all plans |

Not shown in `PauseDisabledState` (project paused 90+ days, compute
stopped — `pg_dump` would fail anyway).

### What the component does

- Fetches the project's direct connection settings via
`useProjectSettingsV2Query`
- Builds a connection URI with a `[YOUR-PASSWORD]` placeholder (password
is never stored or displayed)
- Shows three shell commands to dump roles, schema, and data separately
— mirroring the [logical backup
docs](https://supabase.com/docs/guides/platform/backups)
- Optionally shows a **Reset database password** button (gated on
`UPDATE projects` permission); shown in the paused state, hidden
elsewhere via `showResetPassword={false}`
- Includes inline guidance to percent-encode special characters in the
password

### Shell safety

The generated `--db-url` values are wrapped in single quotes to prevent
shell metacharacter expansion when users paste and run the commands.
`npx supabase login` is intentionally omitted — the `--db-url` flag
authenticates directly against Postgres and does not require a Supabase
account.

### Backup button behaviour in failed states

The "Download backup" button in `PauseFailedState` and
`RestoreFailedState` now always stays enabled:
- **Backup available** — downloads immediately (unchanged)
- **No backup / physical backups** — opens a dialog with CLI
instructions instead of silently failing

## How to test

**Delete project flow**
1. Open any project → Settings → General → Delete project
2. Verify the CLI backup section appears with the project's host, port,
user, and db name pre-filled
3. Verify no Reset database password button is shown

**Paused project**
1. Open a paused project (`ProjectPausedState`) — verify CLI
instructions appear with the "Your project must be resumed before
running these commands." note
2. Open a project paused for 90+ days (`PauseDisabledState`) — verify
CLI instructions do not appear

**Failed states**
1. Simulate a pause-failed or restore-failed state
2. If a downloadable backup exists — "Download backup" downloads it
directly
3. Block the backup API or use a project with physical backups —
"Download backup" should open the CLI instructions dialog

**Error state**
1. Block the project settings API call (DevTools → Network → block
request)
2. Verify an error message appears with a link to Database settings
3. Verify a loading skeleton shows while the request is in flight

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-04-15 16:39:32 +02:00

79 lines
2.5 KiB
TypeScript

import { describe, expect, it } from 'vitest'
import {
buildDirectPostgresConnectionUri,
buildLogicalBackupShellScript,
DB_PASSWORD_PLACEHOLDER,
} from '../../components/layouts/ProjectLayout/LogicalBackupCliInstructions.utils'
describe('buildDirectPostgresConnectionUri', () => {
it('builds a valid postgresql URI from settings', () => {
const uri = buildDirectPostgresConnectionUri({
db_user: 'postgres',
db_host: 'db.abcdef.supabase.co',
db_port: 5432,
db_name: 'postgres',
})
expect(uri).toBe(
`postgresql://postgres:${DB_PASSWORD_PLACEHOLDER}@db.abcdef.supabase.co:5432/postgres`
)
})
it('uses the password placeholder, never a real password', () => {
const uri = buildDirectPostgresConnectionUri({
db_user: 'postgres',
db_host: 'db.abcdef.supabase.co',
db_port: 5432,
db_name: 'postgres',
})
expect(uri).toContain(DB_PASSWORD_PLACEHOLDER)
expect(uri).not.toContain('secret')
})
it('includes a non-default port', () => {
const uri = buildDirectPostgresConnectionUri({
db_user: 'postgres',
db_host: 'db.abcdef.supabase.co',
db_port: 6543,
db_name: 'postgres',
})
expect(uri).toContain(':6543/')
})
})
describe('buildLogicalBackupShellScript', () => {
const testUri = `postgresql://postgres:${DB_PASSWORD_PLACEHOLDER}@db.abcdef.supabase.co:5432/postgres`
it('produces exactly three commands', () => {
const script = buildLogicalBackupShellScript(testUri)
expect(script.split('\n')).toHaveLength(3)
})
it('wraps the connection URI in single quotes to prevent shell expansion', () => {
const script = buildLogicalBackupShellScript(testUri)
for (const line of script.split('\n')) {
expect(line).toContain(`'${testUri}'`)
}
})
it('dumps roles, schema, and data in that order', () => {
const [roles, schema, data] = buildLogicalBackupShellScript(testUri).split('\n')
expect(roles).toContain('--role-only')
expect(roles).toContain('-f roles.sql')
expect(schema).toContain('-f schema.sql')
expect(data).toContain('--data-only')
expect(data).toContain('-f data.sql')
})
it('excludes storage vector tables from the data dump', () => {
const [, , data] = buildLogicalBackupShellScript(testUri).split('\n')
expect(data).toContain('-x "storage.buckets_vectors"')
expect(data).toContain('-x "storage.vector_indexes"')
})
it('does not include npx supabase login', () => {
const script = buildLogicalBackupShellScript(testUri)
expect(script).not.toContain('supabase login')
})
})