CVMs

Redeploy CVM from a specific revision

Changed on

Switch/rollback a CVM to a specified app revision (compose_hash). Does not change encrypted env unless encrypted_env is supplied. A mismatch between allowed_envs and the last env write is rejected unless encrypted_env is supplied or allow_env_mismatch is true.

post/api/v1/cvms/{cvm_id}/revisions/{revision_id}/redeploy

Request

Path parameters

cvm_idstring required
revision_idstring required

External AppRevisionId (prefix 'rev_'). Fully prefixed string required; bare payloads and raw integers are rejected.

Example:rev_0123abcd

Query parameters

transaction_hashstring nullable

Optional transaction hash proving on-chain compose hash registration

Request body

encrypted_envstring nullable

Optional encrypted env blob. When omitted, rollback keeps the CVM's current encrypted env. Supply a blob only to deliberately roll env back.

allow_env_mismatchboolean

Continue even when this revision's allowed_envs differ from the last env write. Ignored when encrypted_env is supplied.

Response

Activation initiated

unknown required

Changes