Surface the Infrastructure registry page at the (sub)group levels
Context
The Terraform registry is used to publish, share, and discover Terraform modules. You can publish and download those modules from your GitLab project.
Problem to solve
The problem occurs for customers that have a complex group->sub-group->project structure. For example, one customer with thousands of projects has no way of viewing all of the Terraform modules that exist within a given group or sub-group. So, it's really inefficient when trying to find or validate a given module. It is also frustrating when you try to create a new module, but can't because the name has already been used in another project, but you'd have no way of knowing that unless you searched every project.
Proposal
Proposal
The GitLab UI will have a group-level view of the Terraform Registry. This group-level view will aggregate packages that exist at the sub-group and project levels. This will allow customers to quickly view, search, and discover Terraform modules that exist at the project level.
Note, that module visibility will still follow the GitLab permissions according to: https://docs.gitlab.com/ee/user/packages/package_registry/#package-registry-visibility-permissions
Metrics
Measure page views to the Terraform registry page and clicks throughout all interactions on the page.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.