Skip to content

Split DeleteOrphansScanFindingLicenseScanningApprovalRules2 migration

What does this MR do and why?

Even though versions (timestamps) of the migrations are in the expected order, somehow adding the uniq index migration preceded 20230721095222 for some SM instances.

Since it shouldn't hurt (without knowing why the migrations were not run in the expected order), this MR splits the migration to enqueue the BBMs separately and backport this change to %16.5.

More info can be found in this thread.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #437291 (closed)

Edited by Prabakaran Murugesan

Merge request reports