[go: up one dir, main page]
Skip to content

Manually update vulnerabillity_reads

Adrien Narinesinghrequested to merge
handle-vulnerability-read-changes-from-all-sources into master

What does this MR do and why?

This MR updates all services where vulnerability_reads records need to be created or updated and uses the new Vulnerabilities:Reads:UpsertService to do so instead of the existing database trigger mechanic.

Additionally, it is necessary to ensure that all services can and do deactivate the database trigger in response to the turn_off_vulnerability_read_create_db_trigger_function feature flag so that we can ensure that DB trigger is not handling it. Finding these locations can be hard, so a mechanic was introduced to cause transactions to fail for the needed models to identify these locations and pass the needed flag.

Closes #541894. Closes #548737 (closed).

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.

Edited by Gregory Havenga

Merge request reports