Backend: Backfill data to populate partner, community, unverified
Summary
This issue is to backfill data so that appropriate badging displays for any partner, community or unverified components.
Proposal
TBD - A discussion needs to take place to determine the strategy around how this data backfill should happen in the database.
Confirm purpose and User Reception (how does this benefit the user?)
Since components already exist that should be denoted as partner, community and unverified, having badges denote them as such in the future by backfilling these flags will allow the user to know what type of component they are viewing.
Additional details
Some relevant technical details, if applicable, such as:
- Does this need a feature flag?
- Does there need to be an associated instrumentation issue created related to this work?
- Is there an example response showing the data structure that should be returned (new endpoints only)?
- What permissions should be used?
- Is this EE or CE?
-
EE -
CE
-
- Additional comments:
Implementation Table
| Issue | Link | Notes |
|---|---|---|
Backend: Add verification_level database field to catalog_resources table |
#434053 (closed) | Blocks all |
verification_level is populated |
||
verified |
||
| Backend: Expose field in GraphQL | #434059 (closed) | in parallel |
Backend: create table ci_catalog_verified_namespaces
|
#439390 (closed) | Blocks #432272 (closed) #433299 (closed) |
| Frontend: Sort component by "verified author" components | #432272 (closed) | Blocked by #439390 (closed) |
partner, community, unverified |
||
Verified Creator badge for display |
||
| Backend: Implement search algorithm for recommended | TBD | TBD |
Links/References
Edited by Mark Nuzzo