[PR #88] [MERGED] fix(snapshot): export s3-marked OSS-managed rootfs layers as images

bsakaguchi commented

2026-10-29 14:20:37 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/AgentENV/pull/88
Author: @blahgeek
Created: 7/30/2026
Status: ✅ Merged
Merged: 7/31/2026
Merged by: @yingdi-shan

Base: main ← Head: z1k/fix-snapshot-export-s3-marked-oss-managed.jj-mr-wnqxlutvlzsl

📝 Commits (1)

8538ce9 fix(snapshot): export s3-marked OSS-managed rootfs layers as images

📊 Changes

2 files changed (+76 additions, -11 deletions)

View changed files

📝 src/snapshot/image_export/service.rs (+61 -0)
📝 src/snapshot/image_export/target.rs (+15 -11)

📄 Description

aenv-snapshot-image rejected committed snapshots whose OSS backend records managed layers without local files as external refs carrying the synthetic managed-layers s3 repoBlobUrl. Treat those refs as managed-layer lookups (bytes addressed by digest in the managed-layer store) and skip them during target registry inference.

What

Why

Closes #

Scope and non-goals

Design and behavior changes

Compatibility and operations

Public API or generated protocol:
Configuration or defaults:
Snapshot manifest, artifact layout, or storage format:
Upgrade and rollback:
Host requirements, permissions, ports, or dependencies:

Validation

make fmt
make clippy
make test-unit
Relevant Rust integration tests
make -C services test (required when services/ changes)
Generated clients/server regenerated with the documented make target
Documentation updated
Benchmarks or performance comparison completed

Commands and results:

Skipped checks and reasons:

Risks and reviewer notes

Checklist

The PR contains one coherent change and no unrelated formatting or refactoring.
New behavior is covered by tests, or I explained why testing is impractical.
Logs and examples contain no credentials, tokens, or private registry information.
I did not manually edit generated code without updating its source and regenerating it.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/AgentENV/pull/88 **Author:** [@blahgeek](https://github.com/blahgeek) **Created:** 7/30/2026 **Status:** ✅ Merged **Merged:** 7/31/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `z1k/fix-snapshot-export-s3-marked-oss-managed.jj-mr-wnqxlutvlzsl` --- ### 📝 Commits (1) - [`8538ce9`](https://github.com/kvcache-ai/AgentENV/commit/8538ce9924ef99a549ccaf3c53145dab345ea6a1) fix(snapshot): export s3-marked OSS-managed rootfs layers as images ### 📊 Changes **2 files changed** (+76 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `src/snapshot/image_export/service.rs` (+61 -0) 📝 `src/snapshot/image_export/target.rs` (+15 -11) </details> ### 📄 Description aenv-snapshot-image rejected committed snapshots whose OSS backend records managed layers without local files as external refs carrying the synthetic managed-layers s3 repoBlobUrl. Treat those refs as managed-layer lookups (bytes addressed by digest in the managed-layer store) and skip them during target registry inference. ## What  ## Why  ## Related issue  Closes # ## Scope and non-goals  ## Design and behavior changes  ## Compatibility and operations  - Public API or generated protocol: - Configuration or defaults: - Snapshot manifest, artifact layout, or storage format: - Upgrade and rollback: - Host requirements, permissions, ports, or dependencies: ## Validation  - [ ] `make fmt` - [ ] `make clippy` - [ ] `make test-unit` - [ ] Relevant Rust integration tests - [ ] `make -C services test` (required when `services/` changes) - [ ] Generated clients/server regenerated with the documented `make` target - [ ] Documentation updated - [ ] Benchmarks or performance comparison completed Commands and results: ```text ``` Skipped checks and reasons: ## Risks and reviewer notes  ## Checklist - [ ] The PR contains one coherent change and no unrelated formatting or refactoring. - [ ] New behavior is covered by tests, or I explained why testing is impractical. - [ ] Logs and examples contain no credentials, tokens, or private registry information. - [ ] I did not manually edit generated code without updating its source and regenerating it. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi