-
- Downloads
There was an error fetching the commit references. Please try again later.
Add `first` & `latest` pipeline IDs to `vulnerability_occurrences`
We want to drop the `vulnerability_occurrence_pipelines` table. In order to do this, we still need the first and latest pipeline ID stored somewhere to support the existing feature-set These columns should both be nullable, as continuous scanning or alternative scan sources will not have a pipeline_id to associate. resolves: #422382 Changelog: added
Showing
- db/migrate/20240214035028_add_first_and_latest_pipeline_id_to_vulnerability_occurrences.rb 26 additions, 0 deletions...st_and_latest_pipeline_id_to_vulnerability_occurrences.rb
- db/schema_migrations/20240214035028 1 addition, 0 deletionsdb/schema_migrations/20240214035028
- db/structure.sql 2 additions, 0 deletionsdb/structure.sql
db/schema_migrations/20240214035028
0 → 100644
Please register or sign in to comment