GraphQL - Add findingTokenStatus to PipelineSecurityReportFindingType
What does this MR do and why?
Add findingTokenStatus to PipelineSecurityReportFindingType. We'll use this later to display the finding token status/validity check status in the MR security modal, see !197545 (closed) and !197546
Note for reviewer: Because of multiversion compatibility requirements, if this backend graphql change slips to 18.3, we won’t be able to start the frontend work until 18.4. But if we can squeeze it into 18.2, we can safely do the resolver logic and frontend work in 18.3. If there are minor changes needed, I plan to address them in follow-up MR !197545 (closed). As long as the GraphQL field gets deployed in 18.2, everything else (resolver logic, other backend work, and frontend) can go in next milestone.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.