Skip to content

Remove schema from background migrations template

What does this MR do and why?

Remove schema from background migrations template

Background migrations by default use latest if the schema is not set, see https://gitlab.com/gitlab-org/gitlab/-/blob/v16.3.0-ee/spec/spec_helper.rb?ref_type=tags#L144.

Using a specific schema could lead to false positives, for example, a column referenced on the background migration could be modified which would break the specs. This would make the background migration fail if this one is still in progress. The error will be noticeable at merge request level if the background migration were to use the 'latest' schema, and would be silently skipped if the background migration was using a specific migration number.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Mayra Cabrera

Merge request reports