[UX] resolve --dry-run output full dependency graph as a plan, consumable by unpack

Aperta
#9 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
8/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli, devtools

Direzione di ricerca

The issue asks for --dry-run to print the full resolved dependency graph as a plan that unpack can consume, with a lockfile as the shared artifact. Read the resolve, unpack and dry-run paths first to see how they currently duplicate fetch and verify logic. The open questions on metadata-only lookup, conflicting pins and removal previews need maintainer decisions before any code. Work should not start until those are settled.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary 🤖

grcli should behave like a typical package manager for Gemara artifact dependencies: resolve → lock → sync. Given a root artifact, compute its full transitive dependency graph, record what was found as a durable lockfile, then make a local directory match that lockfile exactly -- fetch what's missing, verify it, and remove what's no longer needed. Fetching/verifying/writing should be one reusable operation driven entirely by a lockfile -- not something resolve and unpack each implement separately.

The lockfile should also work disconnected from the network: a fully offline directory (or archive) plus its lockfile should be independently re-verifiable by anyone, with no need to trust whoever produced it.

Why

A caller should be able to see the full resolved dependency set — every version, every conflict, every license — before any content is fetched. That preview becomes the input to the fetch/sync step, so the expensive graph-walk only ever has to happen once per resolution. It also gives a natural hook for auditing (license compatibility across the whole graph) before committing to anything, and gives downstream tooling (policy engines, offline/airgapped consumers) a stable, inspectable artifact to build on instead of having to re-derive it.

This covers some of the authoring flows for compliance-as-code: reading a single artifact, and syncing a project's full dependency set to disk. grcli's responsibility ends at producing a correct, verified, synced tree plus its lockfile. Aggregation or derived artifacts can be part of consumer workflow.

Open Questions

  • Can the full resolved graph (versions, digests, licenses) be known without fetching full artifact content, or does that require a cheaper metadata-only lookup per dependency?
  • When the resolved graph disagrees with itself (same dependency pinned to two different versions), should the fetch/sync step refuse to proceed, or proceed and surface the disagreement for something downstream to handle?
  • When syncing a local directory to match a lockfile, should content no longer referenced by the lockfile be removed automatically, and if so, how does a caller preview that removal before it happens?
  • Should re-verifying an already-fetched, offline dependency set require any network access at all, or must it be fully self-contained?
Lingua principale
Go
Stelle
0
Fork
2
Merge medio
1g 15h
PR unite (30g)
6

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di gemaraproj/grcli

Tutte le issue di gemaraproj/grcli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.