Ensure security finding partition numbers are selected from the right db

What does this MR do and why?

After an initial attempt to fix the incorrect selection of partition numbers when defining the partition number allocation for security scans posed other new risks, @stomlinson advised a smaller change to fix the issue of non-partitioning of security findings while we consider better solutions for fixing the implicit connection of the SharedModel class as a separate endeavour.

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.

Merge request reports

Loading