Skip to content

Commit ba8c74b

Browse files
kvapslexfrei
authored andcommitted
docs(marketplace): point the Repositories view to Admin
The dashboard moves the Repositories view from the Marketplace sidebar to Admin, under Administration (cozystack/cozystack#4286). The connect guide only said to open it "from the sidebar", and it sits in the Marketplace section, so readers would look for it in the wrong place. Assisted-by: LLM Signed-off-by: Andrei Kvapil <[email protected]>
1 parent 192ceeb commit ba8c74b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎content/en/docs/next/marketplace/connecting.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ A `SECRET` column reading `<none>` on a private repository means the credential
9696

9797
## Connect from the dashboard
9898

99-
The dashboard "Repositories" view is backed by the `Tap` resource and covers the same flow without the CLI. Open it from the sidebar, choose **Connect**, and provide the `oci://` reference and, for a private repository, the name of a pull-credential `Secret` in `cozy-system`. Connected repositories are listed with their status; a tapped repository still connecting or blocked by a name collision shows its message there, and tapped repositories can be disconnected from the same view.
99+
The dashboard "Repositories" view is backed by the `Tap` resource and covers the same flow without the CLI. Open **Admin** → **Administration** → **Repositories**, choose **Connect**, and provide the `oci://` reference and, for a private repository, the name of a pull-credential `Secret` in `cozy-system`. Connected repositories are listed with their status; a tapped repository still connecting or blocked by a name collision shows its message there, and tapped repositories can be disconnected from the same view.
100100

101101
Two differences from the CLI. The dashboard skips the structural validation `cozypkg tap` runs, so a repository whose charts are broken connects cleanly and fails later, when an application from it is installed. And connecting here only records the intent: the call writes the Flux source and returns `connecting`, and the cluster then pulls the artifact, checks its digest against the source, reads the `PackageSource` resources and applies the same name-collision check in the background. So an unreachable reference is accepted rather than refused up front the way the CLI refuses it; the outcome arrives as the repository's status in the view, and `cozypkg list` does not show the source until that has finished.
102102

0 commit comments

Comments
 (0)