[package]
name = "cloud-media-bootproof"
# 0.1.0 (2026-09-29): TEST-ONLY. Holds `tests/image_writer_boot.rs`, moved AS IS
# out of `nornir-build-thing/tests/` — the proof that the four cloud media
# `nornir_build_thing::image_writer` writes BOOT back under QEMU+OVMF.
#
# Why a crate of its own: the proof needs BOTH nornir-build-thing (the writer
# under test) and korp-installer's `gpt` / `esp` / `kvmproof` (the one GPT
# writer, ESP assembler and boot harness in the constellation — LAW 5, not
# re-rolled). korp-installer lives in tunnr since 2026-09-26 and path-deps back
# into edda, so:
# * by PATH (`../../../tunnr/crates/korp-installer`) it closes an edda -> tunnr
# -> edda path cycle and edda stops resolving from any non-canonical checkout
# (nornir-release-core/tests/no_path_dep_on_our_consumer.rs);
# * by REGISTRY as a dev-dep OF nornir-build-thing it drags registry
# nornir-build-thing 0.1.24 (korp-boot-bios 0.1.2 depends on it) into
# nornir-build-thing's own test graph, and `cargo test -p nornir-build-thing`
# fails with "specification is ambiguous".
# Here the registry copy is harmless: this crate is not named nornir-build-thing.
# Same shape as appliance-grow's `korp-installer = "=0.1.20"`.
version = "0.1.0"
edition = "2024"
rust-version = "1.85"
license = "MIT OR Apache-2.0"
repository = "https://git.gunnar.rs/nordisk/edda"
description = "Test-only: boots the four cloud media nornir-build-thing's image_writer produces (VHD, AWS raw, GCE tarball, qcow2) back under QEMU+OVMF."
publish = false
[dependencies]
[dev-dependencies]
nornir-build-thing = { path = "../nornir-build-thing" }
# `default-features = false`: no znippy (no OpenZL C toolchain), no `image`
# codec, no forge. Its `gpt.rs`, `esp.rs` and `kvmproof.rs` are byte-identical
# to tunnr's working tree at 330206a. When tunnr bumps korp-installer, bump this.
korp-installer = { version = "0.2.0", default-features = false }
# Scratch dirs for the disk, the media and the EFI payload build.
tempfile = "3"