You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 25f8f11
Browse filesBrowse the repository at this point in the historyBrowse files
fix(marketplace): reconcile tap texts with no-install-on-connect
Removing on-connect auto-registration made several user-facing and doc texts
wrong: they promised that tapping registers a repository's apps in the catalog
and runs its charts. Tapping now installs nothing, so the texts told operators to
wait for apps that never appear.
Reword the `cozypkg tap`/`untap` help, the tap success output (now printing a
`cozypkg add <name>` line per materialized PackageSource), the `cozypkg init`
scaffold README, the packages-index trust model, the dashboard Repositories
banner and per-repository empty state, and the stale re-registration code
comments. No behaviour changes beyond the added `cozypkg add` hint in the tap
output.
Assisted-by: LLM
Signed-off-by: IvanHunters <[email protected]>
(cherry picked from commit 2f39e30)
returnfmt.Errorf("failed to create Package %s: %w", pkgName, err)
530
530
}
531
531
if!created {
532
-
// The materializer auto-created the registration Package between the
533
-
// List above and this Create, so this run did not take ownership of it
534
-
// (its markers are not shed). Re-run so the reopen path pins it -- for a
535
-
// non-default variant to apply the choice, and for the default variant so
536
-
// a later privileged flip does not de-register this deliberate install.
537
-
_, _=fmt.Fprintf(os.Stderr, "Package %s was just auto-registered; re-run 'cozypkg add %s' to install variant %q as your own\n", pkgName, pkgName, variant)
532
+
// A Package of this name appeared between the List above and this Create
533
+
// (a concurrent add, or a tap-managed registration left by an older
534
+
// Cozystack), so this run did not take ownership of it (its markers are
535
+
// not shed). Re-run so the reopen path pins it -- for a non-default
536
+
// variant to apply the choice, and for the default variant so a later
537
+
// privileged flip does not de-register this deliberate install.
538
+
_, _=fmt.Fprintf(os.Stderr, "Package %s already exists; re-run 'cozypkg add %s' to install variant %q as your own\n", pkgName, pkgName, variant)
_, _=fmt.Fprintf(cmd.OutOrStdout(), "The repository's applications register in the dashboard catalog automatically. A privileged install component is not installed until you confirm it with 'cozypkg add --allow-privileged'. Check the source's events if an app does not appear.\n")
362
+
_, _=fmt.Fprintf(cmd.OutOrStdout(), "Tapping installs nothing. Install an app with:\n")
Copy file name to clipboardExpand all lines: hack/packages-index/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,4 +42,4 @@ Cosign verification is **mandatory** on the gate for both lanes: the trust ancho
42
42
43
43
## Trust model
44
44
45
-
Signature verification happens here, at publication time, not at tap time. `cozypkg tap` and the dashboard connect flow validate an artifact's structure but do not verify its cosign signature: a cluster that taps a listed repository trusts that this index already verified it. The verification points are this CI gate (which pins each release to the entry's recorded identity) and, optionally, Flux `OCIRepository` verification at pull time. Tapping a third-party repository runs its charts in the management cluster, so operators should tap only sources they trust or that appear in a curated index like this one.
45
+
Signature verification happens here, at publication time, not at tap time. `cozypkg tap` and the dashboard connect flow validate an artifact's structure but do not verify its cosign signature: a cluster that taps a listed repository trusts that this index already verified it. The verification points are this CI gate (which pins each release to the entry's recorded identity) and, optionally, Flux `OCIRepository` verification at pull time. Installing an app from a tapped repository runs its charts in the management cluster, so operators should tap only sources they trust or that appear in a curated index like this one.
0 commit comments