Remove alert_message_faq from storage banners

What does this MR do and why?

We noticed that the FAQ link in the storage banners doesn't exist anymore, so we started a discussion in #508743 (comment 2283645097) on how to proceed.

PM and TW decided that we should remove the paragraph related to the FAQ and link the mention of "storage" in the copy to the Storage Usage Quotas docs

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

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

Project Repository Limis

Storage Status Before After
Over limit; no purchased storage repo_limits_over_no_purchased_storage_before repo_limits_over_no_purchased_storage
Approaching purchased storage limit repo_limits_approaching_with_purchased_storage_before repo_limits_approaching_with_purchased_storage
Over purchased storage limit repo_limits_over_with_purchased_storage_before repo_limits_over_with_purchased_storage

Namespace Limis

Storage Status Before After
Approaching limit; no purchased storage namespace_limits_approaching_no_purchased_storage_before namespace_limits_approaching_no_purchased_storage
Over limit; no purchased storage namespace_limits_over_no_purchased_storage_before namespace_limits_over_no_purchased_storage
Approaching purchased storage limit namespace_limits_approaching_with_purchased_storage_before namespace_limits_approaching_with_purchased_storage
Over purchased storage limit namespace_limits_over_with_purchased_storage_before namespace_limits_over_with_purchased_storage

How to set up and validate locally

  1. Prerequisites
    1. Simulate SaaS GitLab.com
    2. Enable these setting in rails console:
      1. Gitlab::CurrentSettings.update!(automatic_purchased_storage_allocation: true)
      2. Gitlab::CurrentSettings.update!(repository_size_limit: 10.gigabytes)
      3. Gitlab::CurrentSettings.update!(enforce_namespace_storage_limit: true)
Project Repository Limits
  1. Create or choose a group to work on. Make note of its id, e.g.: 147 / group = Group.find(147)
  2. Create 2 projects under this group. Make note of its ids, e.g.: 45 and 46
  3. Now add some storage to the projects
    1. Project.find(45).statistics.update(repository_size: 14.gigabytes)
    2. Project.find(46).statistics.update(repository_size: 8.gigabytes)
  4. Propagate this data to the group:
    1. Sidekiq.redis(&:flushdb)
    2. Namespaces::ScheduleAggregationWorker.perform_sync(g.id)
    3. Namespaces::RootStatisticsWorker.perform_sync(g.id)
  5. To add purchased storage, use group.update(additional_purchased_storage_size: 10*1024)
  6. Keep changing the data and compare the screenshots
Namespace Limits
  1. Enable these setting in rails console:
    1. Plan.free.actual_limits.update!(notification_limit: 5*1024)
    2. Plan.free.actual_limits.update!(enforcement_limit: 5*1024)
    3. Plan.free.actual_limits.update!(storage_size_limit: 5*1024)
    4. ::Feature.enable(:namespace_storage_limit)
  2. Create or choose a group to work on. Make note of its id, e.g.: 147 / group = Group.find(147)
  3. Create 2 projects under this group. Make note of its ids, e.g.: 45 and 46
  4. Now add some storage to the projects
    1. Project.find(45).statistics.update(repository_size: 14.gigabytes)
    2. Project.find(46).statistics.update(repository_size: 8.gigabytes)
  5. Propagate this data to the group:
    1. Sidekiq.redis(&:flushdb)
    2. Namespaces::ScheduleAggregationWorker.perform_sync(g.id)
    3. Namespaces::RootStatisticsWorker.perform_sync(g.id)
  6. To add purchased storage, use group.update(additional_purchased_storage_size: 10*1024)
  7. Keep changing the data and compare the screenshots
Edited by Sheldon Led

Merge request reports

Loading