delete

Delete an artifact. —yes skips the confirmation.

Usage: factrove delete <id> [--yes | --force] [--json]

Deletes an artifact, its stored HTML, and any public link. A terminal asks
for confirmation. --yes and --force skip that prompt.

Options:
  --yes    Delete without a confirmation prompt.
  --force  Same as --yes.
  --json   Print one JSON line.

​

Accepted flags

The help text above is exact. These flags are also accepted, including ones that help text does not list.

• --yes — Delete without a confirmation prompt.
• --force — Same as —yes. Delete without a confirmation prompt.
• --json — Print one JSON line (alias: —output json).
• --output <json|text> — Print one JSON line when the value is json. —output text is the plain output.
• --api-url, --endpoint-url <origin> — API origin (alias: —endpoint-url).
• --profile <name> — Credentials profile (default: default). Accepted on every command. Help lists it on configure.
• --quiet — Accepted on upload, get, share, list, rename, and delete. It does not hide their output. Help does not list it. configure rejects it.
• -h, --help — Show help.

​

Behavior

Plain success prints Deleted {id}. --json prints one line, {"deleted":true,"id":"…"}. The API response itself is empty.

A terminal asks Delete artifact {id}? and continues only for y or yes. Anything else cancels. When stdin is not a terminal, pass --yes or --force. Those two flags do the same thing.

Delete removes the artifact row and the current HTML object. A public link stops working. The CLI does not keep a local index such as factrove.md, so there is no local file to update. Only the owner can delete. Anyone else gets 404 ARTIFACT_NOT_FOUND, including an organization admin. A storage failure keeps the artifact row. The stored HTML may already be gone, so retry the delete. If concurrent replaces prevent deletion after eight attempts, the API returns 409 CONTENT_CONFLICT. Retry the delete.

​

Related

• CLI
• Delete an artifact