Connect Infrastructure Registry list to api correctly
What does this MR do?
In this MR we add a config parameter to the packages app, when this flag is set to true
the app overrides the package_type
passed to the API to only fetch infrastructure registry related packages (terraform in this case)
Note that this FE work is behind a feature flag: infrastructure_registry_page
=> #326460 (closed)
How to test
- Enter the rails console:
rails c
- Enable the feature flag:
Feature.enable(:infrastructure_registry_page)
- Find the first project in your GDK:
p = Project.first
- Import needed dependency:
require "#{Rails.root}/spec/support/factory_bot"
- Create a bunch of terraform modules:
FactoryBot.create_list(:terraform_module_package, 25,:with_build, project: p)
- Navigate to the
first project
(usually gitlab-org/gitlab-test) => Packages & Registries => Infrastructure Registry
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Related to #323418 (closed)
Edited by Nicolò Maria Mezzopera