Carina

destroy

Destroy all resources defined in the configuration. Carina computes a destroy plan and, after confirmation, deletes every managed resource recorded in state for the given directory.

Usage

carina destroy [OPTIONS] [PATH]

PATH defaults to . (current directory). It must be a directory containing one or more .crn files.

Flags

--auto-approve

Skip the interactive confirmation prompt and proceed with the destroy immediately.

--lock <BOOL>

Enable or disable state locking during the destroy. Defaults to true. Disable only when you know no other process is touching the same state.

--refresh <BOOL>

Refresh state from the cloud provider before computing the destroy plan. Defaults to true.

--force

Destroy even resources that have prevent_destroy = true in their directives block.

Backend Drift

Before destroying resources, Carina checks the current project backend against carina-backend.lock. If the backend changed, destroy refuses and points at carina init --migrate-state .; this prevents silently reading or writing state from the new backend before migration is explicit.

Examples

Destroy everything in the current directory after confirmation:

carina destroy

Destroy without prompting (e.g. in a CI teardown step):

carina destroy --auto-approve

Destroy a specific directory and bypass prevent_destroy:

carina destroy --force path/to/config