pub struct Storage {
pub uuid: String,
pub title: String,
pub size_gib: u64,
pub tier: String,
pub zone: String,
pub state: String,
pub kind: StorageKind,
pub labels: Vec<Label>,
pub origin: Option<String>,
pub created_ms: u64,
pub import: Option<Import>,
pub transition: Option<Transition>,
}Fields§
§uuid: String§title: String§size_gib: u64§tier: String§zone: String§state: String§kind: StorageKind§labels: Vec<Label>§origin: Option<String>The volume this was made from. On a Resize Backup it points at the
boot volume that was resized — which, once that server is deleted, names
a uuid that no longer resolves (behaviour 9, and
Fault::OrphanResizeBackup makes it so immediately).
created_ms: u64Virtual ms, rendered as created. It IS sent — measured against the
live account 2026-09-20 on both GET /1.3/storage/private and
GET /1.3/storage/{uuid}. This crate used to withhold it and claim the
provider did; Fault::WithholdCreatedField now takes it away only when
armed by name, as a hypothesis.
import: Option<Import>The direct-upload session, if one was ever opened on this volume.
It has its OWN clock, and that is the point. MEASURED on the live
estate: a 43 485 184-byte ISO was created 09:36:16Z and completed 09:36:21Z — five seconds — and then the STORAGE sat in syncing for
roughly 100 to 130 seconds more before it turned online. The poller
read syncing at 65 s and at 97 s while this object already said
completed. A mock that turned the storage online when the upload
finished would hide the entire cost, which is all of the cost.
transition: Option<Transition>