Skip to content

Enable delayed deletion of projects by default

Production Change

Change Summary

Enable the instance setting in the admin panel to enable delayed deletion of projects by default in newly created groups.

Related to gitlab-org/gitlab#255449 (closed)

Change Details

  1. Services Impacted - ServiceGitLab Rails
  2. Change Technician - @engwan
  3. Change Reviewer - @cmiskell
  4. Time tracking - 15
  5. Downtime Component - None

Detailed steps for the change

Pre-Change Steps - steps to be completed before execution of the change

Estimated Time to Complete (mins) - 15

  • Set label changein-progress on this issue
  • Notify support team in #support_gitlab-com that we are enabling this setting

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 5

Post-Change Steps - steps to take to verify the change

Estimated Time to Complete (mins) - 5

  • Create a new top-level group
  • Apply a premium license to the group
  • Visit http://gitlab.com/groups/the_group_path/-/edit
  • Expand "Permissions, LFS, 2FA"
  • Verify that "Enable delayed project deletion" is checked

Rollback

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

Estimated Time to Complete (mins) - 5

Monitoring

Key metrics to observe

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

Summary of infrastructure changes

  • Does this change introduce new compute instances? No
  • Does this change re-size any existing compute instances? No
  • Does this change introduce any additional usage of tooling like Elastic Search, CDNs, Cloudflare, etc? No

Summary of the above

Changes checklist

  • This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities.
  • This issue has the change technician as the assignee.
  • Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed.
  • This Change Issue is linked to the appropriate Issue and/or Epic
  • Necessary approvals have been completed based on the Change Management Workflow.
  • 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.
  • 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.)
  • 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.
Edited by Heinrich Lee Yu