What a Profile deletion would trash right now, with a revision the caller echoes back so a confirmation taken over a stale list is refused.
API reference sections
Schema
ProfileDeletionPreview
Type object
Shape
| Field | Type | Description |
|---|---|---|
| targetsrequired | array of WorkspaceId | The live Workspaces currently placed under the Profile, by root placement, in listing order. |
| placement_revisionrequired | integer (uint64, >= 0) | BLAKE3 (first 64 bits) over the Profile unit's revision and, per target in order, its id, its durable revision and its overlay bytes. Any move, trash, restore or overlay write on an involved unit changes it; the number itself means nothing. |
{
"targets": [
"00000000-0000-4000-8000-000000000000"
],
"placement_revision": 0
}The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.
Used by
Generated from contract version 1. Last updated .
