Docs: Migrate virtual registry documentation
-
Start this issue's title with
Docs:orDocs feedback:.
Problem to solve
In !207964 (merged), we added the UI for Maven virtual registries. We decided to keep all UI steps in the Maven-specific virtual registry page. However, a lot of these sections include UI instructions that are generic. As we implement more package-specific docs to the virtual registries, we need to migrate these generic sections to the Virtual registries center page.
Further details
Soon, we will merge a new page that documents the container virtual registry. Although the UI is still not available for container virtual registries, migrating content from Maven will require some major refactoring. If we start working on the content migration now, documenting the container virtual registry UI will be a lot less work to write and review.
Proposal
To get ahead, we need to execute the following changes:
- Add a container virtual registry link to the list of supported packages under Supported package formats for virtual registries.
-
Migrate the following generic virtual registries content in Maven virtual registres to Virtual registries:
- Authentication - authentication is similar/the same for different package formats: pick your preferred token type, select the right scopes, and make sure you have the right permissions. We can consolidate container and Maven VR authentication content into this parent topic as a SSOT. Authentication will become a prerequisite to access the registry.
- View virtual registries
- Edit a virtual registry
- Delete a virtual registry
- View upstream registries
- Edit an upstream registry
- Reorder upstream registries - link to this section from Virtual registry workflows section; it mentions the ordered list system.
- View cached packages (Goes under Caching system)
- Delete cache entries (Goes under Caching system)