nschema destroy

Drop all managed schema objects from the target database. Prompts for confirmation before making changes unless --auto-approve is given.

nschema destroy

Purely destructive

destroy is purely destructive and is exempt from the destructive-action policy — it’s the intended escape hatch for tearing a managed schema back down. To preview exactly what it would drop without running it, use plan --destroy.

Needs

A live database (a PROVIDER postgres block) the tool can write to, and a source for the schema to tear down — a configured state store (BACKEND file or BACKEND s3), or, with no store, your *.sql files to fall back on.

When a state store is configured it is refreshed after the teardown.

Options

• --scope <name> — limit the teardown to specific namespaces. May be repeated.
• --auto-approve — skip the confirmation prompt. Required for non-interactive runs.

Like a declined apply, a declined destroy makes no changes and exits 1.