Release migrating projects with GitLab Migration to open beta

Current state

bulk_import_project FF has been fully rolled out on gitlab.com.

Spikes in related failures are being observed.

Aim

We want to release migrating projects with GitLab Migration (which is behind bulk_import_project FF) to open beta.

In this issue we plan next steps required to do that.

Consideration points

We should consider all the points from open beta definition:

  • not ready for production use
  • unstable and can cause performance and stability issues
  • configuration and dependencies unlikely to change
  • features and functions unlikely to change
  • data loss not likely
  • support on a commercially-reasonable effort basis
  • documentation for the feature should reflect beta status
  • can be behind a feature flag that is on by default and the UI should reflect beta status
  • can be behind a toggle that is off by default and the UI should reflect beta status
  • can be announced in a release post that reflects beta status

plus any additional considerations/concerns and steps to be done raised:

  • add an application admin setting (proposed, issue ) -

to be able to enable/disable GitLab Migration in admin settings, similar to other importers. It can be beneficial before enabling feature flag on self-managed. In case if we need to disable it, the self-managed users can do it in admin settings

  • concerns about rolling out the feature on production and enabling it by default on self-managed almost at the same time (raised):

We recently had two S1 security incidents related to GitLab migration which make us less confident in rolling this out in a "big bang"

Next steps

  • Complete rollout of FF - to 100%
  • Verify no new issues are reported
  • Add an application admin setting
  • Prepare documentation for the feature that reflect its beta status
  • Adjust UI to reflect feature's beta status
  • Manual testing from a security perspective performed by AppSec
  • Set default_enabled: true for the FF in order to roll it out to self-managed
  • Merge documentation update for the feature that reflect its beta status (can this be done earlier, before setting default_enabled: true for the FF, as on SaaS it's already rolled out?)
  • Announce it in a release post that reflects beta status
Edited by Magdalena Frankiewicz