Struct GetImageBuildResponseWire 

pub struct GetImageBuildResponseWire {
    pub image_arn: String,
    pub image_version: String,
    pub build_id: String,
    pub build_state: String,
    pub architecture: String,
    pub chipset: String,
    pub chipset_generation: String,
    pub created_at: f64,
    pub state_reason: Option<String>,
    pub snapshot_build: Option<SnapshotBuild>,
}

GetMicrovmImageBuildOutput, which is MicrovmImageBuildSummary plus one member.

Why this is not the same type as the summary

It differs by exactly one member — snapshotBuild — and that member is the whole reason to make the call: it is the only place any API reports a size for anything this platform builds. Nothing on GetMicrovmImage, GetMicrovm, or either listing carries a byte count, and the three figures here are the quantities the snapshot read, write, and storage line items bill on (crate::cost). A separate type rather than an Option field on the summary, because the summary is a listing shape that never carries one, and an Option there would read as “the service sometimes omits the sizes” rather than “the listing does not have this member”.

Every other member is required and identical to the summary’s, so the same eight are bare fields here.

Fields

image_arn: String

image_version: String

build_id: String

build_state: String

architecture: String

chipset: String

chipset_generation: String

The Graviton generation this build targeted. One CreateMicrovmImage fans out into one build per generation, so a version’s builds differ only in this member — and a partially failed image, one generation succeeding and the other not, is a state a caller should expect (docs/PLATFORM.md).

created_at: f64

state_reason: Option<String>

snapshot_build: Option<SnapshotBuild>

The three snapshot sizes, when the service reports them.

Option because the model does not mark it required, and because a failed build answers a partial one: measured 2026-08-16 on a real FAILED build, snapshotBuild carried codeInstallSizeInBytes alone with no memory and no disk snapshot — which is exactly the shape of a build that installed the code and then never produced a snapshot.

Implementations

impl GetImageBuildResponseWire

pub fn describe(&self) -> String

The build as a diagnosis reads it: the generation, the state, the reason when there is one, and the sizes when the service reported them.

The generation is in the line because a version has one build per Graviton generation and they can disagree — “the build failed” is ambiguous where “generation 4 failed” is not. Sizes are appended only when present, for the reason the absent-reason rule gives: a rendered 0 bytes would claim a measurement the service did not make.

Trait Implementations

impl Clone for GetImageBuildResponseWire

fn clone(&self) -> GetImageBuildResponseWire

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for GetImageBuildResponseWire

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for GetImageBuildResponseWire

fn deserialize<__D>( __deserializer: __D, ) -> Result<GetImageBuildResponseWire, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for GetImageBuildResponseWire

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.