Prepare offline bundles with fresh Git and locked Cargo #195

Open
opened 2026-10-24 15:44:10 +02:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Version-four bundles have reusable source, Git object and Cargo preparation APIs, but using them still requires custom Python scaffolding. A maintained command should prepare a complete offline bundle and compare the fresh results with its admitted inputs.

Proposed behavior and scope

Add an offline preparation command with an explicit inventory and digest, three input roots, source-role selections, pinned tools, fresh output directories and finite resource allowances. Prepare fresh Git contexts and source trees, install admitted locks without refreshing them, and compare actual Cargo completion with the recorded source, lock and graph identities. Publish a bounded descriptive report after successful retirement.

Authority, security and reliability

Tools and inputs have explicit paths, lengths and hashes. The command has no network acquisition or executable-discovery fallback. It borrows live admission and completion owners; reports cannot recreate them. Keep first failures, partial output and independent cleanup uncertainty. Check actual selected parents and protected directory views before effects. Caller-controlled stable namespaces, trusted runtime inputs and enclosing physical resource limits remain explicit requirements.

Acceptance criteria

  • Require version-four inputs, exact role coverage and explicit finite work, storage, stream and execution allowances; refuse incomplete selections before native effects.
  • Select exact tools and fresh local output routes without configuration, credential, cache or acquisition fallback.
  • Prepare actual Git contexts and source owners, consume admitted locks without refresh, and compare the complete fresh Cargo results through their live owners.
  • Share one scoped input-directory census across the declared batch while preserving per-effect parent, source and native-input checks; never assume equivalent directory views from matching inode numbers.
  • Preserve original deadlines, first errors and once-only independent cleanup through denial, cancellation, resource exhaustion and report-write failure.
  • Document the command and add meaningful loose, packed, shallow, multi-role and failure-path controls.

Alternatives and tradeoffs

The existing CI gateway discovers catalogs and tools and supports acquisition. Keeping its interface separate makes the offline command's inputs and failure behavior easier to review. Fresh preparation costs storage and native work; copying a prior Cargo home or accepting a successful-looking report would hide those inputs.

Tracking and rollout

Builds on original Git object transport. Tracked by Phase 6 completion and the compatibility changes. Guest tools, complete image construction and both required builds inside EriX remain separate requirements.

## Problem and motivation Version-four bundles have reusable source, Git object and Cargo preparation APIs, but using them still requires custom Python scaffolding. A maintained command should prepare a complete offline bundle and compare the fresh results with its admitted inputs. ## Proposed behavior and scope Add an offline preparation command with an explicit inventory and digest, three input roots, source-role selections, pinned tools, fresh output directories and finite resource allowances. Prepare fresh Git contexts and source trees, install admitted locks without refreshing them, and compare actual Cargo completion with the recorded source, lock and graph identities. Publish a bounded descriptive report after successful retirement. ## Authority, security and reliability Tools and inputs have explicit paths, lengths and hashes. The command has no network acquisition or executable-discovery fallback. It borrows live admission and completion owners; reports cannot recreate them. Keep first failures, partial output and independent cleanup uncertainty. Check actual selected parents and protected directory views before effects. Caller-controlled stable namespaces, trusted runtime inputs and enclosing physical resource limits remain explicit requirements. ## Acceptance criteria - [ ] Require version-four inputs, exact role coverage and explicit finite work, storage, stream and execution allowances; refuse incomplete selections before native effects. - [ ] Select exact tools and fresh local output routes without configuration, credential, cache or acquisition fallback. - [ ] Prepare actual Git contexts and source owners, consume admitted locks without refresh, and compare the complete fresh Cargo results through their live owners. - [ ] Share one scoped input-directory census across the declared batch while preserving per-effect parent, source and native-input checks; never assume equivalent directory views from matching inode numbers. - [ ] Preserve original deadlines, first errors and once-only independent cleanup through denial, cancellation, resource exhaustion and report-write failure. - [ ] Document the command and add meaningful loose, packed, shallow, multi-role and failure-path controls. ## Alternatives and tradeoffs The existing CI gateway discovers catalogs and tools and supports acquisition. Keeping its interface separate makes the offline command's inputs and failure behavior easier to review. Fresh preparation costs storage and native work; copying a prior Cargo home or accepting a successful-looking report would hide those inputs. ## Tracking and rollout Builds on [original Git object transport](https://git.erikinkinen.fi/erix/integration/issues/194). Tracked by [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65) and the [compatibility changes](https://git.erikinkinen.fi/erix/integration/pulls/12). Guest tools, complete image construction and both required builds inside EriX remain separate requirements.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:22 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#195
No description provided.