Restructure Vulnerability Finding Models
Why are we doing this work
The vulnerability findings architecture is getting fairly complex with the move from raw_metadata
to individual models. This proposal is to restructure the Vulnerabilities module such that the various Finding elements fall under the Finding class to better organize the code. This is already in work in #239179.
- FindingIdentifier => Finding::Identifier
- FindingLink => Finding::Link
- FindingPipeline => Finding::Pipeline
- FindingRemediation => Finding::Remediation
- FindingSignature => Finding::Signature
Relevant links
Non-functional requirements
-
Testing: Specs will need to be updated as well. -
Make sure Secure E2E specs are not broken with this change. Trigger Package and QA
manually in the MR pipeline
Implementation plan
Each of these can/should be done in a separate MR.
-
backend FindingIdentifier => Finding::Identifier -
Change file location -
Update class name -
Update references in the code
-
-
backend FindingLink => Finding::Link -
Change file location -
Update class name -
Update references in the code
-
-
backend FindingPipeline => Finding::Pipeline -
Change file location -
Update class name -
Update references in the code
-
-
backend FindingRemediation => Finding::Remediation -
Change file location -
Update class name -
Update references in the code
-
-
backend FindingSignature => Finding::Signature -
Change file location -
Update class name -
Update references in the code
-
Verification steps
Edited by Thiago Figueiró