<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ### Problem to solve Provide an easy way for users to manage their corpus'. ### Proposal Implement the designs from the MVC (https://www.figma.com/file/eSIeuIPKFwEDs4X9ky2O5E/Corpus-Registry?node-id=156%3A0) which was previously designed as part of this [design issue](https://gitlab.com/gitlab-org/gitlab/-/issues/231232) YAML interface as discussed in https://gitlab.com/gitlab-org/gitlab/-/issues/280590 ```yaml fuzzinputs_target: extends: .fuzz_base image: registry.gitlab.com/gitlab-org/security-products/analyzers/gitlab-cov-fuzz/golang:1.12-buster-llvm9 variables: COVFUZZ_USE_CORPUS_REGISTRY: true COVFUZZ_CORPUS_NAME: "foobar_corpus" ``` If `COVFUZZ_USE_CORPUS_REGISTRY` is not present, default to the original behavior which looked in the repo and with artifacts. ### Frontend Implementation Plan (Remaining Issues for MVC) | Issue | Weight | Milestone | Description | ------ | ------ | ------ | ----- | | https://gitlab.com/gitlab-org/gitlab/-/issues/342433 | ~"frontend-weight::3" | %"14.5" | Upload Corpus | https://gitlab.com/gitlab-org/gitlab/-/issues/342580 | ~"frontend-weight::2" | %"14.5" | Commit Corpus | https://gitlab.com/gitlab-org/gitlab/-/issues/345088 | ~"frontend-weight::3" | %"14.5" | Swap out mock table data for real query | https://gitlab.com/gitlab-org/gitlab/-/issues/345090 | ~"frontend-weight::3" | %"14.6" | Corpus table pagination | https://gitlab.com/gitlab-org/gitlab/-/issues/342583 | ~"frontend-weight::2" | %"14.6" | Modal validation errors | https://gitlab.com/gitlab-org/gitlab/-/issues/345089 | ~"frontend-weight::3" | %"14.7" | Inline delete | https://gitlab.com/gitlab-org/gitlab/-/issues/352073 | - | %"14.8" | https://gitlab.com/gitlab-org/gitlab/-/issues/352073+| | https://gitlab.com/gitlab-org/gitlab/-/issues/350974 | ~"frontend-weight::2" | %"14.8" | Testing in Staging | https://gitlab.com/gitlab-org/gitlab/-/issues/350975 | ~"frontend-weight::2" | %"14.8" | Testing in Production | https://gitlab.com/gitlab-org/gitlab/-/issues/328418 | ~"backend-weight::2" | %"14.8" | GraphQL Feature flag enablement (Global) | https://gitlab.com/gitlab-org/gitlab/-/issues/349014 | ~"frontend-weight::2" | %"14.8" | UI Feature flag enablement (First to test project, then global) | https://gitlab.com/gitlab-org/gitlab/-/issues/341489 | ~documentation | %14.8 | Documentation ### Post MVC - Cleanup and V2 iteration Covered in a cleanup epic https://gitlab.com/groups/gitlab-org/-/epics/6902 ### Backend Implementation Plan [Fuzz Corpus Backend technical implementation](https://gitlab.com/gitlab-org/gitlab/-/issues/273169) ### User Permissions User must be able to see the security dashboard to interact with the corpus management.