Struct DeleteImageResponseWire 

pub struct DeleteImageResponseWire {
    pub image_identifier: String,
    pub state: String,
}

DeleteMicrovmImageOutput.

Kept and read, rather than deleted as dead

This struct was parsed nowhere: try_delete_image discarded the reply, so the shape existed and no code could observe drift in it. The choice was to delete it or to read it, and reading it wins on one specific case — a 2xx whose state is a *_FAILED spelling. That is the service accepting the delete request and refusing the work, and without the readback it is indistinguishable from a successful delete: delete_image answers true, teardown reports clean, and an image keeps billing. This project has had exactly that failure once already, in tools/verify-clean.py, which is why the account is now asked what leaked rather than trusted to have been cleaned.

DELETING and DELETED are both success and the call site treats them alike. The deletion is asynchronous, so DELETING is the ordinary answer; treating it as incomplete would make the retry loop re-issue a delete that is already in progress and then report failure on the ConflictException that comes back.

Fields

image_identifier: String

state: String

Trait Implementations

impl Clone for DeleteImageResponseWire

fn clone(&self) -> DeleteImageResponseWire

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for DeleteImageResponseWire

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for DeleteImageResponseWire

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.