Migrate advisories into a central `advisories`, similar to `policy_violations`
As well as having the raw data to i.e. perform follow-up queries, we should also pre-compute the tables to much further simplify all the cases where advisories data is consumed.
This would look identical to policy_violations
, but would be for non-policy related things (while still allowing advisory_type = POLICY
)
Alternatively
Rename advisories
to custom_advisories
and then use advisories
for the actual generated ones.
Will need to think about allowing tuning for --upcoming-days
i.e. for "90 days until EOL"
Edited by Jamie Tanna