Skip to content

Setup routing for virtual registries

Overview

To start building out the UI for Virtual registries design we will need to setup some Rails routes and controllers.

Proposal

At the virtual registries level, we need 3 pages. A list page, new & edit virtual registry pages.

  • The list page ideally needs to be built in Vue with a GraphQL API backing the data, we can explore doing a haml implementation with limited functionality.
  • The new & edit pages can be built using haml templates with form submission to create & edit rules.

So we need a route, controller and HAML files to render the templates.

  • Add /virtual_registries route to the groups scope. Example: /groups/<group-name>/-/virtual_registries

Checks required

Route should be available

  • only for root groups
  • only when feature flags virtual_registry_maven and ui_for_virtual_registry are enabled
  • licenced feature packages_virtual_registry is available
  • when Gitlab.config.dependency_proxy.enabled is true
  • has read_virtual_registry permission
Edited by Rahul Chanila