Enable the "GitLab Migration" importer on .com in the admin application settings

Production Change

Change Summary

We recently added "GitLab Migration" to the list of "Importer sources" that can be controlled in the Admin settings.

With this control in place, we plan on removing bulk_imports feature flag which is currently enabled by default on .com. Going forward, administrators should utilize the UI toggle to easily enable/disable GitLab migration (like any other importer).

The setting needs to be enabled first, before we deploy changes that respect the setting and before the feature flag bulk_imports gets removed so the behavior on .com remains unchanged (i.e., GitLab Migration should be enabled).

Change Details

1. Services Impacted - List services
2. Change Technician - @cmcfarland
3. Change Reviewer - @mchacon3
4. Time tracking - 10m
5. Downtime Component - N/A

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 5

• Set label changein-progress /label ~change::in-progress
• Navigate to GitLab.com Admin Interface
• Navigate to Settings --> General, expand Visibility and access controls
• Check the Enabled checkbox for Enable migrating GitLab groups and projects by direct transfer
• Set label changecomplete /label ~change::complete

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 5

• Uncheck the Enabled checkbox for Enable migrating GitLab groups and projects by direct transfer
• Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

• Metric: Metric Name
  • Location: Dashboard URL
  • What changes to this metric should prompt a rollback: Describe Changes

Change Reviewer checklist

C4 C3 C2 C1:

• Check if the following applies:
  • The scheduled day and time of execution of the change is appropriate.
  • The change plan is technically accurate.
  • The change plan includes estimated timing values based on previous testing.
  • The change plan includes a viable rollback plan.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change.

C2 C1:

• Check if the following applies:
  • The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
  • The change plan includes success measures for all steps/milestones during the execution.
  • The change adequately minimizes risk within the environment/service.
  • The performance implications of executing the change are well-understood and documented.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change.
    • If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
  • The change has a primary and secondary SRE with knowledge of the details available during the change window.
  • The labels blocks deployments and/or blocks feature-flags are applied as necessary

Change Technician checklist

• Check if all items below are complete:
  • The change plan is technically accurate.
  • This Change Issue is linked to the appropriate Issue and/or Epic
  • Change has been tested in staging and results noted in a comment on this issue.
  • A dry-run has been conducted and results noted in a comment on this issue.
  • The change execution window respects the Production Change Lock periods.
  • For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
  • For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
  • For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
  • For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
  • Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
  • There are currently no active incidents that are severity1 or severity2
  • If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.