GovOPlaN/govoplan-admin
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Expose searchable module catalog compatibility

Browse Source
This commit is contained in:
zemion
2026-08-06 22:42:13 +02:00
parent 1e55a80d3c
commit 9d522ef6e0
8 changed files with 501 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+11 -6
View File
@@ -54,12 +54,17 @@ admin UI records operator intent and queues or renders commands for the trusted
installer process described in
`/mnt/DATA/git/govoplan-core/docs/MODULE_ARCHITECTURE.md`.
Catalog entries show whether the package is already installed and whether the
directory advertises another version. Selecting an entry preserves its signed
registry URLs and integrity evidence in the reviewed plan. The installer, not
the browser or API request, downloads and verifies those artifacts. On a shared
or Kubernetes deployment, the same plan requires a new immutable image
composition instead of changing one running replica.
Catalog entries can be searched by module, package, repository, or tag and
filtered by availability, installed state, update state, and blockers. Each row
shows its signed source revision and immutable artifact digest together with
configuration requirements and release notes when the publisher supplies them.
Withdrawn entries and targets with missing dependencies, incompatible named
interfaces, or an unsupported current-version window cannot be added to a plan.
Selecting an eligible entry preserves its signed registry URLs and integrity
evidence in the reviewed plan. The installer, not the browser or API request,
downloads and verifies those artifacts. On a shared or Kubernetes deployment,
the same plan requires a new immutable image composition instead of changing
one running replica.
The WebUI presents the lifecycle as five derived stages: plan, preflight,
installer request, daemon execution, and run evidence. The projection resets