Merge branch 'eread/badge-rake-task-topics' into 'master'

Add tier badges to Rake task topics

Closes #207893

See merge request gitlab-org/gitlab!30586

doc/.vale/gitlab/spelling-exceptions.txt

@@ -237,6 +237,7 @@ Qualys
 Rackspace
 Raketask
 Raketasks
+reachability
 rebase
 rebased
 rebases
@@ -372,6 +373,7 @@ unstage
 unstaged
 unstages
 unstaging
+untarred
 untracked
 untrusted
 unverified

doc/administration/auth/ldap-troubleshooting.md

@@ -312,7 +312,7 @@ things to check to debug the situation.
   interval](ldap-ee.md#adjusting-ldap-group-sync-schedule) for the group to
   sync. To speed up the process, either go to the GitLab group **Settings ->
   Members** and press **Sync now** (sync one group) or [run the group sync Rake
-  task](../raketasks/ldap.md#run-a-group-sync) (sync all groups).
+  task](../raketasks/ldap.md#run-a-group-sync-starter-only) (sync all groups).
 
 If all of the above looks good, jump in to a little more advanced debugging in
 the rails console.
@@ -352,7 +352,7 @@ GitLab syncs the `admin_group`.
 
 NOTE: **NOTE:**
 To sync all groups manually when debugging is unnecessary, [use the Rake
-task](../raketasks/ldap.md#run-a-group-sync) instead.
+task](../raketasks/ldap.md#run-a-group-sync-starter-only) instead.
 
 The output from a manual [group sync](ldap-ee.md#group-sync) can show you what happens
 when GitLab syncs its LDAP group memberships against LDAP.

doc/administration/raketasks/check.md

-# Integrity check Rake task
+# Integrity check Rake task **(CORE ONLY)**
 
 GitLab provides Rake tasks to check the integrity of various components.
 

doc/administration/raketasks/github_import.md

-# GitHub import
+# GitHub import **(CORE ONLY)**
 
 > [Introduced]( https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10308) in GitLab 9.1.
 

doc/administration/raketasks/ldap.md

-# LDAP Rake tasks
+# LDAP Rake tasks **(CORE ONLY)**
 
 The following are LDAP-related Rake tasks.
 
@@ -28,7 +28,7 @@ limit by passing a number to the check task:
 rake gitlab:ldap:check[50]
 ```
 
-## Run a group sync
+## Run a group sync **(STARTER ONLY)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/14735) in [GitLab Starter](https://about.gitlab.com/pricing/) 12.2.
 

doc/administration/raketasks/maintenance.md

-# Maintenance Rake tasks
+# Maintenance Rake tasks **(CORE ONLY)**
 
 GitLab provides Rake tasks for general maintenance.
 

doc/administration/raketasks/praefect.md

-# Praefect Rake Tasks
+# Praefect Rake Tasks **(CORE ONLY)**
 
 > [Introduced]( https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28369) in GitLab 12.10.
 

doc/administration/raketasks/storage.md

-# Repository storage Rake tasks
+# Repository storage Rake tasks **(CORE ONLY)**
 
 This is a collection of Rake tasks you can use to help you list and migrate
 existing projects and attachments associated with it from Legacy storage to

doc/administration/raketasks/uploads/migrate.md

-# Uploads migrate Rake tasks
+# Uploads migrate Rake tasks **(CORE ONLY)**
 
 `gitlab:uploads:migrate` migrates uploads between different storage types.
 

doc/administration/raketasks/uploads/sanitize.md

-# Uploads sanitize Rake tasks
+# Uploads sanitize Rake tasks **(CORE ONLY)**
 
 Since GitLab 11.9, EXIF data is automatically stripped from JPG or TIFF image uploads.
 

doc/raketasks/README.md

@@ -16,11 +16,11 @@ GitLab Rake tasks are performed using:
 The following are available Rake tasks:
 
 | Tasks                                                                                               | Description                                                                               |
-|:-------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------|
+|:----------------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------|
 | [Back up and restore](backup_restore.md)                                                            | Back up, restore, and migrate GitLab instances between servers.                           |
 | [Clean up](cleanup.md)                                                                              | Clean up unneeded items from GitLab instances.                                            |
 | [Development](../development/rake_tasks.md)                                                         | Tasks for GitLab contributors.                                                            |
-| [Elasticsearch](../integration/elasticsearch.md#gitlab-elasticsearch-rake-tasks)           | Maintain Elasticsearch in a GitLab instance.                                              |
+| [Elasticsearch](../integration/elasticsearch.md#gitlab-elasticsearch-rake-tasks) **(STARTER ONLY)** | Maintain Elasticsearch in a GitLab instance.                                              |
 | [Enable namespaces](features.md)                                                                    | Enable usernames and namespaces for user projects.                                        |
 | [General maintenance](../administration/raketasks/maintenance.md)                                   | General maintenance and self-check tasks.                                                 |
 | [Geo maintenance](../administration/raketasks/geo.md) **(PREMIUM ONLY)**                            | [Geo](../administration/geo/replication/index.md)-related maintenance.                    |

doc/raketasks/backup_restore.md

-# Backing up and restoring GitLab
+# Backing up and restoring GitLab **(CORE ONLY)**
 
 GitLab provides Rake tasks for backing up and restoring GitLab instances.
 
@@ -687,7 +687,7 @@ before restoring the backup.
 You need to have a working GitLab installation before you can perform
 a restore. This is mainly because the system user performing the
 restore actions (`git`) is usually not allowed to create or delete
-the SQL database it needs to import data into ('gitlabhq_production').
+the SQL database it needs to import data into (`gitlabhq_production`).
 All existing data will be either erased (SQL) or moved to a separate
 directory (repositories, uploads).
 
@@ -713,7 +713,7 @@ more of the following options:
   Read what the [backup timestamp is about](#backup-timestamp).
 - `force=yes` - Does not ask if the authorized_keys file should get regenerated and assumes 'yes' for warning that database tables will be removed, enabling the "Write to authorized_keys file" setting, and updating LDAP providers.
 
-If you are restoring into directories that are mountpoints you will need to make
+If you are restoring into directories that are mount points, you will need to make
 sure these directories are empty before attempting a restore. Otherwise GitLab
 will attempt to move these directories before restoring the new data and this
 would cause an error.

doc/raketasks/cleanup.md

-# Clean up
+# Clean up **(CORE ONLY)**
 
 GitLab provides Rake tasks for cleaning up GitLab instances.
 
@@ -7,9 +7,11 @@ GitLab provides Rake tasks for cleaning up GitLab instances.
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/36628) in GitLab 12.10.
 
 DANGER: **Danger:**
-Do not run this within 12 hours of a GitLab upgrade. This is to ensure that all background migrations have finished, which otherwise may lead to data loss.
+Do not run this within 12 hours of a GitLab upgrade. This is to ensure that all background migrations
+have finished, which otherwise may lead to data loss.
 
-When you remove LFS files from a repository's history, they become orphaned and continue to consume disk space. With this Rake task, you can remove invalid references from the database, which
+When you remove LFS files from a repository's history, they become orphaned and continue to consume
+disk space. With this Rake task, you can remove invalid references from the database, which
 will allow garbage collection of LFS files.
 
 For example:

doc/raketasks/features.md

-# Namespaces
+# Namespaces **(CORE ONLY)**
 
 This Rake task enables [namespaces](../user/group/index.md#namespaces) for projects.
 

doc/raketasks/generate_sample_prometheus_data.md

-# Generate sample Prometheus data
+# Generate sample Prometheus data **(CORE ONLY)**
 
 This command will run Prometheus queries for each of the metrics of a specific environment
 for a series of time intervals to now:

doc/raketasks/import.md

-# Import bare repositories
+# Import bare repositories **(CORE ONLY)**
 
 Rake tasks are available to import bare repositories into a GitLab instance.
 

doc/raketasks/list_repos.md

-# Listing repository directories
+# Listing repository directories **(CORE ONLY)**
 
 You can print a list of all Git repositories on disk managed by GitLab.
 

doc/raketasks/user_management.md

-# User management
+# User management **(CORE ONLY)**
 
 GitLab provides Rake tasks for user management.
 

doc/raketasks/x509_signatures.md

-# X509 signatures
+# X509 signatures **(CORE ONLY)**
 
 When [signing commits with x509](../user/project/repository/x509_signed_commits/index.md),
 the trust anchor might change and the signatures stored within the database must be updated.