Preserve sanitized OCI runtime failure details #148

New issue

Closed

opened 2026-05-07 15:06:54 -07:00 by jwilger · 0 comments

jwilger commented

2026-05-07 15:06:54 -07:00

Owner

PR #126 review noted that packaged OCI executor failures should provide meaningful diagnostics.

execute_packaged_oci_runtime_with_executor currently maps any executor OciSetupDiagnostic to a generic message, losing useful non-secret details from run_packaged_oci_runtime_command such as std::io::ErrorKind or runtime exit status.

Keep the existing redaction guarantees, but preserve sanitized failure context so operators can distinguish spawn failures from runtime non-zero exits.

Source feedback: PR #126 comment 2953.

PR #126 review noted that packaged OCI executor failures should provide meaningful diagnostics. `execute_packaged_oci_runtime_with_executor` currently maps any executor `OciSetupDiagnostic` to a generic message, losing useful non-secret details from `run_packaged_oci_runtime_command` such as `std::io::ErrorKind` or runtime exit status. Keep the existing redaction guarantees, but preserve sanitized failure context so operators can distinguish spawn failures from runtime non-zero exits. Source feedback: PR #126 comment 2953.

jwilger added the

bug

label

2026-05-07 15:07:07 -07:00

jwilger referenced this issue

2026-05-07 15:07:36 -07:00

chore: release v0.3.0 #126

jwilger removed the

bug

label

2026-05-08 11:42:28 -07:00

jwilger added this to the 1.0 milestone