In order to for frontend to implement sorting by verified author components in #432272 (closed), this issue is necessary to support that sorting from a backend perspective.
Proposal
We should assign a verification_level to a namespace so that we can cascade the correct catalog_resources.verification_level badge when a new catalog resource is created.
We need to create a table: catalog_verified_namespaces with namespace_id, verification_level, created_at. After this is done, we can use a data migration for SaaS only that adds the components namespaces as verification_level: :gitlab_maintained. The issue for the migration is here: #439392 (closed)
Confirm purpose and User Reception (how does this benefit the user?)
Users will be able to sort in the catalog to find verified authors in their searches.
Additional details
Some relevant technical details, if applicable, such as:
If you are unsure about the correct group, please do not leave the issue without a group label, and refer to
GitLab's shared responsibility functionality guidelines
for more information on how to triage this kind of issue.
Hi @rkadam3 - this is the updated backend issue that we need to start for filtering/sorting/badges (the one I pinged you on in the other issue ... hope you're reading these pings in order ). I split up the work into two issues (one for the table and one for the data migration), but if you feel like both can be done in this issue, go for it. I think either way is fine. I pinged you on this since you were assigned to the other one but let us know if you can't do it and we can figure it out!
Thanks @lauraX - ongoing discussion below around naming conventions for the table but I agree that this can move forward.
@rkadam3 - if you are able to take this on, with #432272 (closed) having candidate16.10 label (the issue it blocks), the sooner we can do this with less data to migrate, the better.
Thanks for the ping @lauraX! Just a small suggestion, would ci_catalog_verified_namespaces be a more descriptive table name? It would better align with the use of namespace_id.
Also, are we only putting root namespaces in this table or nested namespaces as well?
In the former case, we can be more explicit by naming it ci_catalog_verified_root_namespaces.
Thanks @lauraX for updating the description with latest information.
For the MR in this issue, I am just adding the table, so in case things change again, I will make sure that I consider the latest while I start my work on data migration issue - #439392 (closed)
Hi @rkadam3 - yes, now that the table is merged and deployed, we can close the issue which I'll do now. I think that generally we wait to close out the issue until all of the production related tasks are present which is why I tend to apply the workflowverification based on the statuses of related MRs. Thank you for your efforts here.