Skip to content

Frontend: Move shared Catalog components to FOSS

Frédéric Caplette requested to merge 428068-frontend-move-shared-catalog-components-to-foss into master

What does this MR do and why?

Move the CI/CD Catalog client-side code to FOSS folders because the Catalog will now be primarily a FOSS feature &11674 (closed).

This MR takes the Catalog UI components that are not specific to the namespace catalog and moves them to FOSS. This means that the only things left in EE will be:

  • 2 Vue components
  • The JS entry point
  • Graphql queries

The Backend code will also be moved to foss but it is not required before moving these files because the graphql queries will stay in ee. For refrence: !133994 (merged)

Screenshots or screen recordings

No visual changes

How to set up and validate locally

Ensure that the CI catalog works as it used to by following these steps:

  1. Make sure you have an premium license for your GDK
  2. Login as an admin user
  3. Create a few projects that you will be able to convert to Ci resources. Create them under the admin namespace for ease of testing.
  4. Once you have done so, get the ID of the first new project you wanted to convert. Then in Rails console, run:
projects = Project.where("id > ?", your_first_project_id)
projects.each do |project|
  project.update!(description: 'description')  
  ::Ci::Catalog::Resource.new(project_id: project.id).save   
end
  1. Navigate to /$namespace/$project/-/ci/catalog/resources/. Any project under the same namespace will do (in this case, anything under the admin namespace)
  2. Notice that it loads
  3. Click on a resource
  4. Notice that you see the details of the component.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #428068 (closed)

Edited by Frédéric Caplette

Merge request reports