Organization API: Customer Portal: Snapshots

Part of Customer Portal.

GET /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots

Snapshots taken from this server or, with scope=account, every snapshot the account holds, each judged for restoring onto this server.

The account list is the owner's, since those are the only snapshots a restore here would accept; a shared-server viewer asking for it gets this server's own list, the same as the platform client surface.

POST /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots

application/json

GET /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots/estimate

How much of the allowance a snapshot of this server would use.

Its own endpoint rather than a field on the listing, because the figure is read live from Wings: folding it into the list would make the snapshots tab as slow as the slowest node on the fleet, on every load, to answer a question only the create dialog asks.

Deliberately an over-estimate. It is the server's current uncompressed disk usage, and an archive is never larger than what it archives, so a creation that fits on this number cannot push the account over. The retention policy depends on that. What the customer sees is therefore a ceiling, and the dialog says so.

GET /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots/seed

The restore a server ordered from a snapshot is waiting on, or got.

Null for a server ordered the ordinary way, which is nearly all of them.

POST /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots/seed/retry

Run a failed seed again. A failed restore leaves the snapshot unharmed.

DELETE /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots/{snapshot_uuid}

GET /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots/{snapshot_uuid}/download

POST /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots/{snapshot_uuid}/lock

Keep a snapshot, or release it. A locked snapshot is not rotated away.

POST /api/v1/orgs/{org_slug}/portal/servers/{uuid}/snapshots/{snapshot_uuid}/restore

Restore onto this server, from any snapshot this customer owns.

Addressed by the target server because that is what is being overwritten, and what the permission is checked against.

application/json