push

Push a snapshot to remote storage.

Usage

clonit push <target> [snapshot_index] [flags]

Arguments

Argument	Description	Required
`target`	Name of the target	Yes
`snapshot_index`	Index of the snapshot to push	No (defaults to latest)

Flags

Flag	Type	Default	Description
`--no-verify`	bool	`false`	Skip checksum verification after upload

Description

Uploads a snapshot to the remote storage provider configured in the target’s linked storage profile. By default, the latest snapshot is pushed unless a specific snapshot index is provided.

After uploading, a checksum verification is performed to ensure data integrity. Use --no-verify to skip this check.

The target must have a storage profile linked to it. See storage-profile add for configuring storage profiles.

Examples

Push the latest snapshot:

clonit push mydb

Push a specific snapshot by index:

clonit push mydb 0

Push without checksum verification:

clonit push mydb --no-verify

Auto-push

The snapshot-producing commands – build, sanitize, and ephemeral – automatically push the snapshot they produce when the target has a storage profile configured for that snapshot type: originals go to the target’s storage profile, sanitized snapshots only to its sanitized storage profile (no fallback – without the matching profile the snapshot stays local). Auto-push failures never fail the producing command; retry manually with clonit push. To skip auto-push, use the --no-push flag on any of the three commands or set defaults.auto_push: false in the config. See build for the full rules.

Note that manual clonit push differs from auto-push in one way: when pushing a sanitized snapshot for a target that has no sanitized storage profile, manual push falls back to the target’s original storage profile.