[UX] resolve --dry-run output full dependency graph as a plan, consumable by unpack
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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?
- Lenguaje dominante
- Go
- Estrellas
- 0
- Forks
- 2
- Merge medio
- 1 d 15 h
- PR fusionados (30 d)
- 6
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de gemaraproj/grcli
-
grcli cat has a confusing error if you are testing different optionsPosiblemente ocupada @PaarthPandey10 la tomó hace 17 días. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
gemaraproj/grcli#10 · 1 comentario · 1 asignado ·
-
enhancement Stale
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
gemaraproj/grcli#2 · 1 comentario ·
Todos los issues de gemaraproj/grcli
Issues similares
-
Pin and verify Security Insights schema in lintinsights targetPosiblemente ocupada @imshubham22apr-gif la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
gemaraproj/gemara#618 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
a2aproject/a2a-go#597 ·
Los mantenedores suelen responder en 1 día
-
scopes: GetAllowedTopics, GetProtectedTopics, and GetScopedTopics include empty topic names and do not trim whitespace charactersPosiblemente ocupada @patelshivani2283-lab la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area/networking kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 69/100
siderolabs/talos#14972 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día