diff options
141 files changed, 250 insertions, 467 deletions
diff --git a/app/helpers/application_settings_helper.rb b/app/helpers/application_settings_helper.rb index 7c5add687b8..ea6e80091d1 100644 --- a/app/helpers/application_settings_helper.rb +++ b/app/helpers/application_settings_helper.rb @@ -413,7 +413,6 @@ module ApplicationSettingsHelper :throttle_protected_paths_period_in_seconds, :throttle_protected_paths_requests_per_period, :protected_paths_raw, - :protected_paths_for_get_request_raw, :time_tracking_limit_to_hours, :two_factor_grace_period, :update_runner_versions_enabled, diff --git a/app/models/application_setting_implementation.rb b/app/models/application_setting_implementation.rb index fe27ac7989e..a90b65ec473 100644 --- a/app/models/application_setting_implementation.rb +++ b/app/models/application_setting_implementation.rb @@ -379,14 +379,6 @@ module ApplicationSettingImplementation self.protected_paths = strings_to_array(values) end - def protected_paths_for_get_request_raw - array_to_string(protected_paths_for_get_request) - end - - def protected_paths_for_get_request_raw=(values) - self.protected_paths_for_get_request = strings_to_array(values) - end - def notes_create_limit_allowlist_raw array_to_string(notes_create_limit_allowlist) end diff --git a/app/views/admin/application_settings/_protected_paths.html.haml b/app/views/admin/application_settings/_protected_paths.html.haml index ec8536320f7..3a7a951d137 100644 --- a/app/views/admin/application_settings/_protected_paths.html.haml +++ b/app/views/admin/application_settings/_protected_paths.html.haml @@ -4,7 +4,7 @@ %fieldset .form-group = f.gitlab_ui_checkbox_component :throttle_protected_paths_enabled, - _('Enable rate limiting for requests to the specified paths'), + _('Enable rate limiting for POST requests to the specified paths'), help_text: _('Helps reduce request volume for protected paths.') .form-group = f.label :throttle_protected_paths_requests_per_period, 'Maximum requests per period per user', class: 'label-bold' @@ -14,12 +14,8 @@ = f.number_field :throttle_protected_paths_period_in_seconds, class: 'form-control gl-form-input' .form-group = f.label :protected_paths, class: 'label-bold' do - = _('Paths with rate limiting for POST requests') + = _('Paths to protect with rate limiting') = f.text_area :protected_paths_raw, placeholder: '/users/sign_in,/users/password', class: 'form-control gl-form-input', rows: 10 - .form-group - = f.label :protected_paths_for_get_request, class: 'label-bold' do - = _('Paths with rate limiting for GET requests') - = f.text_area :protected_paths_for_get_request_raw, class: 'form-control gl-form-input', rows: 10 %span.form-text.text-muted - relative_url_link = 'https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-a-relative-url-for-gitlab' - relative_url_link_start = '<a href="%{url}" target="_blank" rel="noopener noreferrer">'.html_safe % { url: relative_url_link } diff --git a/doc/administration/audit_event_streaming/audit_event_types.md b/doc/administration/audit_event_streaming/audit_event_types.md index 858d873c435..b69f1815394 100644 --- a/doc/administration/audit_event_streaming/audit_event_types.md +++ b/doc/administration/audit_event_streaming/audit_event_types.md @@ -11,7 +11,7 @@ info: "See the Technical Writers assigned to Development Guidelines: https://abo bundle exec rake gitlab:audit_event_types:compile_docs ---> -# Audit event types **(ULTIMATE ALL)** +# Audit event types **(ULTIMATE)** Audit event types are used to [filter streamed audit events](index.md#update-event-filters). diff --git a/doc/administration/packages/index.md b/doc/administration/packages/index.md index 77730384623..2eb3da4b5d7 100644 --- a/doc/administration/packages/index.md +++ b/doc/administration/packages/index.md @@ -196,6 +196,13 @@ To change the local storage path: ::EndTabs +If you already had packages stored in the old storage path, move everything +from the old to the new location to ensure existing packages stay accessible: + +```shell +mv /var/opt/gitlab/gitlab-rails/shared/packages/* /mnt/packages/ +``` + Docker and Kubernetes do not use local storage. - For the Helm chart (Kubernetes): Use object storage instead. diff --git a/doc/api/group_boards.md b/doc/api/group_boards.md index d27f9330fc1..267b9feb750 100644 --- a/doc/api/group_boards.md +++ b/doc/api/group_boards.md @@ -349,7 +349,7 @@ Example response: } ``` -## Delete a group issue board **(PREMIUM)** +## Delete a group issue board **(PREMIUM ALL)** Deletes a group issue board. diff --git a/doc/api/groups.md b/doc/api/groups.md index df1576b750c..930a682c157 100644 --- a/doc/api/groups.md +++ b/doc/api/groups.md @@ -1169,7 +1169,7 @@ The response is `202 Accepted` if the user has authorization. NOTE: A GitLab.com group can't be removed if it is linked to a subscription. To remove such a group, first [link the subscription](../subscriptions/gitlab_com/index.md#change-the-linked-namespace) with a different group. -## Restore group marked for deletion **(PREMIUM)** +## Restore group marked for deletion **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/33257) in GitLab 12.8. diff --git a/doc/api/projects.md b/doc/api/projects.md index a1eead91417..5bd2ec07647 100644 --- a/doc/api/projects.md +++ b/doc/api/projects.md @@ -1338,7 +1338,7 @@ target the upstream project by default. } ``` -### Templates for issues and merge requests **(PREMIUM)** +### Templates for issues and merge requests **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55718) in GitLab 13.10. @@ -2498,7 +2498,7 @@ DELETE /projects/:id | `permanently_remove` **(PREMIUM)** | boolean/string | no | Immediately deletes a project if it is marked for deletion. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/396500) in GitLab 15.11 | | `full_path` **(PREMIUM)** | string | no | Full path of project to use with `permanently_remove`. [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/396500) in GitLab 15.11. To find the project path, use `path_with_namespace` from [get single project](projects.md#get-single-project) | -## Restore project marked for deletion **(PREMIUM)** +## Restore project marked for deletion **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/32935) in GitLab 12.6. @@ -2877,7 +2877,7 @@ POST /projects/:id/housekeeping | `id` | integer or string | **{check-circle}** Yes | The ID or [URL-encoded path of the project](rest/index.md#namespaced-path-encoding). | | `task` | string | **{dotted-circle}** No | `prune` to trigger manual prune of unreachable objects or `eager` to trigger eager housekeeping. | -## Push rules **(PREMIUM)** +## Push rules **(PREMIUM ALL)** ### Get project push rules @@ -3166,7 +3166,7 @@ Read more in the [Project members](members.md) documentation. Read more in the [Project vulnerabilities](project_vulnerabilities.md) documentation. -## Get a project's pull mirror details **(PREMIUM)** +## Get a project's pull mirror details **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/354506) in GitLab 15.6. @@ -3202,7 +3202,7 @@ Example response: } ``` -## Configure pull mirroring for a project **(PREMIUM)** +## Configure pull mirroring for a project **(PREMIUM ALL)** > - Field `mirror_branch_regex` [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/381667) in GitLab 15.8 [with a flag](../administration/feature_flags.md) named `mirror_only_branches_match_regex`. Disabled by default. > - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/381667) in GitLab 16.0. @@ -3226,7 +3226,7 @@ with the API scope enabled. | `only_mirror_protected_branches`| boolean | **{dotted-circle}** No | Limits mirroring to only protected branches when set to `true`. | | `mirror_branch_regex` | String | **{dotted-circle}** No | Contains a regular expression. Only branches with names matching the regex are mirrored. Requires `only_mirror_protected_branches` to be disabled. | -## Start the pull mirroring process for a Project **(PREMIUM)** +## Start the pull mirroring process for a Project **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/api/protected_branches.md b/doc/api/protected_branches.md index 0ca7bdb663c..6bccc777e04 100644 --- a/doc/api/protected_branches.md +++ b/doc/api/protected_branches.md @@ -310,7 +310,7 @@ Example response: } ``` -### Example with user / group level access **(PREMIUM)** +### Example with user / group level access **(PREMIUM ALL)** Elements in the `allowed_to_push` / `allowed_to_merge` / `allowed_to_unprotect` array should take the form `{user_id: integer}`, `{group_id: integer}`, or `{access_level: integer}`. Each user must have access to the project and each group must [have this project shared](../user/project/members/share_project_with_groups.md). These access levels allow [more granular control over protected branch access](../user/project/protected_branches.md). @@ -357,7 +357,7 @@ Example response: } ``` -### Example with allow to push and allow to merge access **(PREMIUM)** +### Example with allow to push and allow to merge access **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/api/search.md b/doc/api/search.md index a018e904391..06e62d28534 100644 --- a/doc/api/search.md +++ b/doc/api/search.md @@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w Every API call to search must be authenticated. -## Additional scopes **(PREMIUM)** +## Additional scopes **(PREMIUM ALL)** Additional scopes are available for the [Advanced Search API](#advanced-search-api) and [Group Search API](#group-search-api) if @@ -269,7 +269,7 @@ Example response: ] ``` -### Scope: `wiki_blobs` **(PREMIUM)** +### Scope: `wiki_blobs` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -301,7 +301,7 @@ Example response: NOTE: `filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` is intended to be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521). -### Scope: commits **(PREMIUM)** +### Scope: commits **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -336,7 +336,7 @@ Example response: ] ``` -### Scope: blobs **(PREMIUM)** +### Scope: blobs **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -377,7 +377,7 @@ Example response: NOTE: `filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` is intended to be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521). -### Scope: notes **(PREMIUM)** +### Scope: notes **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -660,7 +660,7 @@ Example response: ] ``` -### Scope: `wiki_blobs` **(PREMIUM)** +### Scope: `wiki_blobs` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -692,7 +692,7 @@ Example response: NOTE: `filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` is intended to be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521). -### Scope: `commits` **(PREMIUM)** +### Scope: `commits` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -727,7 +727,7 @@ Example response: ] ``` -### Scope: `blobs` **(PREMIUM)** +### Scope: `blobs` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -768,7 +768,7 @@ Example response: NOTE: `filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` is intended to be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521). -### Scope: `notes` **(PREMIUM)** +### Scope: `notes` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -1019,7 +1019,7 @@ Example response: ] ``` -### Scope: `notes` **(PREMIUM)** +### Scope: `notes` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -1056,7 +1056,7 @@ Example response: ] ``` -### Scope: `wiki_blobs` **(PREMIUM)** +### Scope: `wiki_blobs` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -1105,7 +1105,7 @@ Example response: NOTE: `filename` is deprecated in favor of `path`. Both return the full path of the file inside the repository, but in the future `filename` are intended to be only the filename and not the full path. For details, see [issue 34521](https://gitlab.com/gitlab-org/gitlab/-/issues/34521). -### Scope: `commits` **(PREMIUM)** +### Scope: `commits` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -1140,7 +1140,7 @@ Example response: ] ``` -### Scope: `blobs` **(PREMIUM)** +### Scope: `blobs` **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/api/users.md b/doc/api/users.md index 988504ea0df..9b00dc5c7e0 100644 --- a/doc/api/users.md +++ b/doc/api/users.md @@ -2263,7 +2263,7 @@ Returns: - `403 Forbidden` if not authenticated as an administrator. - `404 User Not Found` if user cannot be found. -## Create a runner **(FREE)** +## Create a runner **(FREE ALL)** Creates a runner linked to the current user. diff --git a/doc/api/visual_review_discussions.md b/doc/api/visual_review_discussions.md index f6d6636280a..5b6cb07897d 100644 --- a/doc/api/visual_review_discussions.md +++ b/doc/api/visual_review_discussions.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w --- <!--- start_remove The following content will be removed on remove_date: '2024-05-22' --> -# Visual Review discussions API (deprecated) **(PREMIUM)** +# Visual Review discussions API (deprecated) **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/18710) in GitLab 12.5. > - [Moved](https://about.gitlab.com/blog/2021/01/26/new-gitlab-product-subscription-model/) to GitLab Premium in 13.9. diff --git a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md index 5494e5fad1c..7164fae10a1 100644 --- a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md +++ b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: howto --- -# Using GitLab CI/CD with a Bitbucket Cloud repository **(PREMIUM)** +# Using GitLab CI/CD with a Bitbucket Cloud repository **(PREMIUM ALL)** GitLab CI/CD can be used with Bitbucket Cloud by: diff --git a/doc/ci/ci_cd_for_external_repos/github_integration.md b/doc/ci/ci_cd_for_external_repos/github_integration.md index feb01a0fc4a..1fad7ad5a53 100644 --- a/doc/ci/ci_cd_for_external_repos/github_integration.md +++ b/doc/ci/ci_cd_for_external_repos/github_integration.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: howto --- -# Using GitLab CI/CD with a GitHub repository **(PREMIUM)** +# Using GitLab CI/CD with a GitHub repository **(PREMIUM ALL)** GitLab CI/CD can be used with **GitHub.com** and **GitHub Enterprise** by creating a [CI/CD project](index.md) to connect your GitHub repository to diff --git a/doc/ci/ci_cd_for_external_repos/index.md b/doc/ci/ci_cd_for_external_repos/index.md index 1906e4e99df..a9093632a8c 100644 --- a/doc/ci/ci_cd_for_external_repos/index.md +++ b/doc/ci/ci_cd_for_external_repos/index.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: index, howto --- -# GitLab CI/CD for external repositories **(PREMIUM)** +# GitLab CI/CD for external repositories **(PREMIUM ALL)** >[Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/4642) in GitLab 10.6. diff --git a/doc/ci/components/index.md b/doc/ci/components/index.md index 6faae18dbbc..4a739bdfcf6 100644 --- a/doc/ci/components/index.md +++ b/doc/ci/components/index.md @@ -336,7 +336,7 @@ We recommend adopting at least the `MAJOR.MINOR` format. For example: `2.1`, `1.0.0`, `1.0.0-alpha`, `2.1.3`, `3.0.0-rc.1`. -## CI/CD Catalog **(PREMIUM)** +## CI/CD Catalog **(PREMIUM ALL)** The CI/CD Catalog is a list of [components repositories](#components-repository), each containing resources that you can add to your CI/CD pipelines. diff --git a/doc/ci/environments/deployment_approvals.md b/doc/ci/environments/deployment_approvals.md index 2a9b381c517..2933b25e09b 100644 --- a/doc/ci/environments/deployment_approvals.md +++ b/doc/ci/environments/deployment_approvals.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w description: Require approvals prior to deploying to a Protected Environment --- -# Deployment approvals **(PREMIUM)** +# Deployment approvals **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/343864) in GitLab 14.7 with a flag named `deployment_approvals`. Disabled by default. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/347342) in GitLab 14.8. diff --git a/doc/ci/environments/environments_dashboard.md b/doc/ci/environments/environments_dashboard.md index ce219e5d746..e98205f45b9 100644 --- a/doc/ci/environments/environments_dashboard.md +++ b/doc/ci/environments/environments_dashboard.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: reference --- -# Environments Dashboard **(PREMIUM)** +# Environments Dashboard **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/3713) in GitLab 12.5. diff --git a/doc/ci/environments/kubernetes_dashboard.md b/doc/ci/environments/kubernetes_dashboard.md index ce69ba71c48..98b6731e469 100644 --- a/doc/ci/environments/kubernetes_dashboard.md +++ b/doc/ci/environments/kubernetes_dashboard.md @@ -22,6 +22,10 @@ For Flux users, the synchronization status of a given environment is not display > - Filtering resources by namespace [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/403618) in GitLab 16.2 [with a flag](../../administration/feature_flags.md) named `kubernetes_namespace_for_environment`. Disabled by default. > - Filtering resources by namespace [enabled by default](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127043) in GitLab 16.3. Feature flag `kubernetes_namespace_for_environment` removed. +> - Selecting the related Flux resource [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/128857) in GitLab 16.3 [with a flag](../../administration/feature_flags.md) named `flux_resource_for_environment`. Disabled by default. + +FLAG: +On self-managed GitLab, by default selecting a Flux resource is not available. To make it available, an administrator can [enable the feature flag](../../administration/feature_flags.md) named `flux_resource_for_environment`. On GitLab.com, this feature is not available. Configure a dashboard to use it for a given environment. You can configure dashboard for an environment that already exists, or @@ -40,6 +44,7 @@ Prerequisites: 1. Select **Edit**. 1. Select a GitLab agent for Kubernetes. 1. Optional. From the **Kubernetes namespace** dropdown list, select a namespace. +1. Optional. From the **Flux resource** dropdown list, select a Flux resource. 1. Select **Save**. ### The environment doesn't exist @@ -50,6 +55,7 @@ Prerequisites: 1. Complete the **Name** field. 1. Select a GitLab agent for Kubernetes. 1. Optional. From the **Kubernetes namespace** dropdown list, select a namespace. +1. Optional. From the **Flux resource** dropdown list, select a Flux resource. 1. Select **Save**. ## View a dashboard @@ -63,7 +69,8 @@ To view a configured dashboard: ### Flux sync status -> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/391581) in GitLab 16.3. +> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/391581) in GitLab 16.3. +> - Customizing the name of the Flux resource [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/128857) in GitLab 16.3 [with a flag](../../administration/feature_flags.md) named `flux_resource_for_environment`. Disabled by default. A dashboard displays the sync status of your Flux deployments. diff --git a/doc/ci/environments/protected_environments.md b/doc/ci/environments/protected_environments.md index 41036c1f8fa..fd789ea798d 100644 --- a/doc/ci/environments/protected_environments.md +++ b/doc/ci/environments/protected_environments.md @@ -4,7 +4,7 @@ group: Environments info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Protected environments **(PREMIUM)** +# Protected environments **(PREMIUM ALL)** [Environments](../environments/index.md) can be used for both testing and production reasons. diff --git a/doc/ci/examples/authenticating-with-hashicorp-vault/index.md b/doc/ci/examples/authenticating-with-hashicorp-vault/index.md index 188d0897937..737c95cf747 100644 --- a/doc/ci/examples/authenticating-with-hashicorp-vault/index.md +++ b/doc/ci/examples/authenticating-with-hashicorp-vault/index.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: tutorial --- -# Authenticating and reading secrets with HashiCorp Vault **(PREMIUM)** +# Authenticating and reading secrets with HashiCorp Vault **(PREMIUM ALL)** WARNING: Authenticating with `CI_JOB_JWT` was [deprecated in GitLab 15.9](../../../update/deprecations.md#old-versions-of-json-web-tokens-are-deprecated) diff --git a/doc/ci/jobs/ci_job_token.md b/doc/ci/jobs/ci_job_token.md index 2b5fdd65747..dee078c21e0 100644 --- a/doc/ci/jobs/ci_job_token.md +++ b/doc/ci/jobs/ci_job_token.md @@ -195,7 +195,7 @@ To configure the job token scope: 1. Optional. Add existing projects to the token's access scope. The user adding a project must have the Maintainer role in both projects. -## Download an artifact from a different pipeline **(PREMIUM)** +## Download an artifact from a different pipeline **(PREMIUM ALL)** > `CI_JOB_TOKEN` for artifacts download with the API was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/2346) in GitLab 9.5. diff --git a/doc/ci/jobs/job_control.md b/doc/ci/jobs/job_control.md index 467e19e6956..770e1d38297 100644 --- a/doc/ci/jobs/job_control.md +++ b/doc/ci/jobs/job_control.md @@ -617,7 +617,7 @@ To run a manual job, you must have permission to merge to the assigned branch: You can also [add custom CI/CD variables when running a manual job](index.md#specifying-variables-when-running-manual-jobs). -### Protect manual jobs **(PREMIUM)** +### Protect manual jobs **(PREMIUM ALL)** Use [protected environments](../environments/protected_environments.md) to define a list of users authorized to run a manual job. You can authorize only diff --git a/doc/ci/pipelines/cicd_minutes.md b/doc/ci/pipelines/cicd_minutes.md index 5ea4844af09..4e822cf3edd 100644 --- a/doc/ci/pipelines/cicd_minutes.md +++ b/doc/ci/pipelines/cicd_minutes.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: reference --- -# Compute quota **(PREMIUM)** +# Compute quota **(PREMIUM ALL)** > [Renamed](https://gitlab.com/groups/gitlab-com/-/epics/2150) from "CI/CD minutes" to "compute quota" or "compute minutes" in GitLab 16.1. diff --git a/doc/ci/pipelines/downstream_pipelines.md b/doc/ci/pipelines/downstream_pipelines.md index 4605e76ae87..fca6e8407ef 100644 --- a/doc/ci/pipelines/downstream_pipelines.md +++ b/doc/ci/pipelines/downstream_pipelines.md @@ -382,7 +382,7 @@ trigger_job: ::EndTabs -### View multi-project pipelines in pipeline graphs **(PREMIUM)** +### View multi-project pipelines in pipeline graphs **(PREMIUM ALL)** After you trigger a multi-project pipeline, the downstream pipeline displays to the right of the [pipeline graph](index.md#visualize-pipelines). @@ -390,7 +390,7 @@ to the right of the [pipeline graph](index.md#visualize-pipelines). In [pipeline mini graphs](index.md#pipeline-mini-graphs), the downstream pipeline displays to the right of the mini graph. -## Fetch artifacts from an upstream pipeline **(PREMIUM)** +## Fetch artifacts from an upstream pipeline **(PREMIUM ALL)** ::Tabs @@ -670,7 +670,7 @@ Upstream pipelines take precedence over downstream ones. If there are two variables with the same name defined in both upstream and downstream projects, the ones defined in the upstream project take precedence. -### Pass dotenv variables created in a job **(PREMIUM)** +### Pass dotenv variables created in a job **(PREMIUM ALL)** You can pass variables to a downstream job with [`dotenv` variable inheritance](../variables/index.md#pass-an-environment-variable-to-another-job) and [`needs:project`](../yaml/index.md#needsproject). These variables are only available in diff --git a/doc/ci/pipelines/index.md b/doc/ci/pipelines/index.md index fc9a01b4ef7..7cde8b50524 100644 --- a/doc/ci/pipelines/index.md +++ b/doc/ci/pipelines/index.md @@ -334,7 +334,7 @@ runners do not use regular runners, they must be tagged accordingly. Review the [deployment safety](../environments/deployment_safety.md) page for additional security recommendations for securing your pipelines. -## Trigger a pipeline when an upstream project is rebuilt **(PREMIUM)** +## Trigger a pipeline when an upstream project is rebuilt **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9045) in GitLab 12.8. diff --git a/doc/ci/pipelines/merge_request_pipelines.md b/doc/ci/pipelines/merge_request_pipelines.md index 7d924e84f63..65a57efbe96 100644 --- a/doc/ci/pipelines/merge_request_pipelines.md +++ b/doc/ci/pipelines/merge_request_pipelines.md @@ -126,7 +126,7 @@ Pipelines for forks display with the **fork** badge in the parent project:  -### Run pipelines in the parent project **(PREMIUM)** +### Run pipelines in the parent project **(PREMIUM ALL)** Project members in the parent project can trigger a merge request pipeline for a merge request submitted from a fork project. This pipeline: diff --git a/doc/ci/pipelines/merge_trains.md b/doc/ci/pipelines/merge_trains.md index c2fdbe3f6e5..c2bf9743e4f 100644 --- a/doc/ci/pipelines/merge_trains.md +++ b/doc/ci/pipelines/merge_trains.md @@ -4,7 +4,7 @@ group: Pipeline Execution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Merge trains **(PREMIUM)** +# Merge trains **(PREMIUM ALL)** NOTE: [In GitLab 16.0 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/359057), the **Start merge train** diff --git a/doc/ci/pipelines/merged_results_pipelines.md b/doc/ci/pipelines/merged_results_pipelines.md index 16120924f37..51678e64b10 100644 --- a/doc/ci/pipelines/merged_results_pipelines.md +++ b/doc/ci/pipelines/merged_results_pipelines.md @@ -4,7 +4,7 @@ group: Pipeline Execution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Merged results pipelines **(PREMIUM)** +# Merged results pipelines **(PREMIUM ALL)** > - [Renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/351192) from `pipelines for merged results` to `merged results pipelines` in GitLab 14.8. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/91849) in GitLab 15.1, merged results pipelines also run on [Draft merge requests](../../user/project/merge_requests/drafts.md). diff --git a/doc/ci/review_apps/index.md b/doc/ci/review_apps/index.md index 4ffa2896db4..d05861818e2 100644 --- a/doc/ci/review_apps/index.md +++ b/doc/ci/review_apps/index.md @@ -191,7 +191,7 @@ After you have the route mapping set up, it takes effect in the following locati - In the blob file view, by selecting **View** (**{external-link}**) next to the file. <!--- start_remove The following content will be removed on remove_date: '2024-05-22' --> -## Visual Reviews (deprecated) **(PREMIUM)** +## Visual Reviews (deprecated) **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/10761) in GitLab 12.0. > - [Moved](https://about.gitlab.com/blog/2021/01/26/new-gitlab-product-subscription-model/) to GitLab Premium in 13.9. diff --git a/doc/ci/secrets/azure_key_vault.md b/doc/ci/secrets/azure_key_vault.md index 4ee9d39d8e3..645ab5db0d1 100644 --- a/doc/ci/secrets/azure_key_vault.md +++ b/doc/ci/secrets/azure_key_vault.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: concepts, howto --- -# Use Azure Key Vault secrets in GitLab CI/CD **(PREMIUM)** +# Use Azure Key Vault secrets in GitLab CI/CD **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/271271) in GitLab and GitLab Runner 16.3. diff --git a/doc/ci/secrets/convert-to-id-tokens.md b/doc/ci/secrets/convert-to-id-tokens.md index 6690113273c..18803d4de72 100644 --- a/doc/ci/secrets/convert-to-id-tokens.md +++ b/doc/ci/secrets/convert-to-id-tokens.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: tutorial --- -# Tutorial: Update HashiCorp Vault configuration to use ID Tokens **(PREMIUM)** +# Tutorial: Update HashiCorp Vault configuration to use ID Tokens **(PREMIUM ALL)** This tutorial demonstrates how to convert your existing CI/CD secrets configuration to use [ID Tokens](../secrets/id_token_authentication.md). diff --git a/doc/ci/secrets/id_token_authentication.md b/doc/ci/secrets/id_token_authentication.md index 2ddf7a9c284..22a260e4bb6 100644 --- a/doc/ci/secrets/id_token_authentication.md +++ b/doc/ci/secrets/id_token_authentication.md @@ -138,7 +138,7 @@ manual_authentication: - my-authentication-script.sh $VAULT_TOKEN $PASSWORD ``` -## Automatic ID Token authentication with HashiCorp Vault **(PREMIUM)** +## Automatic ID Token authentication with HashiCorp Vault **(PREMIUM ALL)** You can use ID tokens to automatically fetch secrets from HashiCorp Vault with the [`secrets`](../yaml/index.md#secrets) keyword. diff --git a/doc/ci/secrets/index.md b/doc/ci/secrets/index.md index f903bcb6785..c184102d948 100644 --- a/doc/ci/secrets/index.md +++ b/doc/ci/secrets/index.md @@ -97,7 +97,7 @@ To configure your Vault server: NOTE: Support for providing these values in the user interface [is tracked in this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/218677). -## Use Vault secrets in a CI job **(PREMIUM)** +## Use Vault secrets in a CI job **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/28321) in GitLab 13.4 and GitLab Runner 13.4. diff --git a/doc/ci/testing/browser_performance_testing.md b/doc/ci/testing/browser_performance_testing.md index 059cd637f9e..9e81f243e50 100644 --- a/doc/ci/testing/browser_performance_testing.md +++ b/doc/ci/testing/browser_performance_testing.md @@ -4,7 +4,7 @@ group: Pipeline Execution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Browser Performance Testing **(PREMIUM)** +# Browser Performance Testing **(PREMIUM ALL)** If your application offers a web interface and you're using [GitLab CI/CD](../index.md), you can quickly determine the rendering performance diff --git a/doc/ci/testing/code_coverage.md b/doc/ci/testing/code_coverage.md index b7a298f6bf2..90a07314083 100644 --- a/doc/ci/testing/code_coverage.md +++ b/doc/ci/testing/code_coverage.md @@ -81,7 +81,7 @@ To view a CSV file of the data, select **Download raw data (`.csv`)**.  -### View history of group code coverage **(PREMIUM)** +### View history of group code coverage **(PREMIUM ALL)** To see the all the project's code coverage under a group over time, you can find view [group repository analytics](../../user/group/repositories_analytics/index.md). @@ -92,7 +92,7 @@ To see the all the project's code coverage under a group over time, you can find You can use [pipeline badges](../../user/project/badges.md#test-coverage-report-badges) to indicate the pipeline status and test coverage of your projects. These badges are determined by the latest successful pipeline. -## Coverage check approval rule **(PREMIUM)** +## Coverage check approval rule **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/15765) in GitLab 14.0. > - [Made configurable in Project Settings](https://gitlab.com/gitlab-org/gitlab/-/issues/331001) in GitLab 14.1. diff --git a/doc/ci/testing/code_quality.md b/doc/ci/testing/code_quality.md index 7df7e075934..1d857b8f543 100644 --- a/doc/ci/testing/code_quality.md +++ b/doc/ci/testing/code_quality.md @@ -68,7 +68,7 @@ issues are marked by an indicator beside the gutter. Hover over the marker for d  -### Pipeline details view **(PREMIUM)** +### Pipeline details view **(PREMIUM ALL)** The full list of Code Quality violations generated by a pipeline is shown in the **Code Quality** tab of the pipeline's details page. The pipeline details view displays all Code Quality findings diff --git a/doc/ci/testing/fail_fast_testing.md b/doc/ci/testing/fail_fast_testing.md index 6b1ed4a594d..733c190616c 100644 --- a/doc/ci/testing/fail_fast_testing.md +++ b/doc/ci/testing/fail_fast_testing.md @@ -4,7 +4,7 @@ group: Pipeline Execution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Fail Fast Testing **(PREMIUM)** +# Fail Fast Testing **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/198550) in GitLab 13.1. diff --git a/doc/ci/testing/load_performance_testing.md b/doc/ci/testing/load_performance_testing.md index dac4dd555b0..549aa10287e 100644 --- a/doc/ci/testing/load_performance_testing.md +++ b/doc/ci/testing/load_performance_testing.md @@ -4,7 +4,7 @@ group: Pipeline Execution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Load Performance Testing **(PREMIUM)** +# Load Performance Testing **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/10683) in GitLab 13.2. diff --git a/doc/ci/testing/metrics_reports.md b/doc/ci/testing/metrics_reports.md index 9257ba8990e..0f1eaedfb78 100644 --- a/doc/ci/testing/metrics_reports.md +++ b/doc/ci/testing/metrics_reports.md @@ -4,7 +4,7 @@ group: Pipeline Execution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Metrics Reports **(PREMIUM)** +# Metrics Reports **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9788) in GitLab 11.10. Requires GitLab Runner 11.10 and above. diff --git a/doc/ci/yaml/artifacts_reports.md b/doc/ci/yaml/artifacts_reports.md index 02e3a3b5767..fa7e941ffe5 100644 --- a/doc/ci/yaml/artifacts_reports.md +++ b/doc/ci/yaml/artifacts_reports.md @@ -55,7 +55,7 @@ GitLab can display the results of one or more reports in: - The pipeline [**Security** tab](../../user/application_security/vulnerability_report/pipeline.md#view-vulnerabilities-in-a-pipeline). - The [security dashboard](../../user/application_security/api_fuzzing/index.md#security-dashboard). -## `artifacts:reports:browser_performance` **(PREMIUM)** +## `artifacts:reports:browser_performance` **(PREMIUM ALL)** > [Name changed](https://gitlab.com/gitlab-org/gitlab/-/issues/225914) from `artifacts:reports:performance` in GitLab 14.0. @@ -258,7 +258,7 @@ the [new method of license scanning](../../user/compliance/license_scanning_of_c <!--- end_remove --> -## `artifacts:reports:load_performance` **(PREMIUM)** +## `artifacts:reports:load_performance` **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35260) in GitLab 13.2. > - Requires GitLab Runner 11.5 and above. @@ -271,7 +271,7 @@ GitLab can display the results of only one report in the merge request GitLab cannot display the combined results of multiple `load_performance` reports. -## `artifacts:reports:metrics` **(PREMIUM)** +## `artifacts:reports:metrics` **(PREMIUM ALL)** The `metrics` report collects [Metrics](../testing/metrics_reports.md). The collected Metrics report uploads to GitLab as an artifact. diff --git a/doc/ci/yaml/index.md b/doc/ci/yaml/index.md index 86cc1e058ef..c4f7e6d6e01 100644 --- a/doc/ci/yaml/index.md +++ b/doc/ci/yaml/index.md @@ -2456,7 +2456,7 @@ In this example: - In GitLab 12.6 and later, you can't combine the [`dependencies`](#dependencies) keyword with `needs`. -#### `needs:project` **(PREMIUM)** +#### `needs:project` **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14311) in GitLab 12.7. @@ -3915,7 +3915,7 @@ job2: - [Create custom collapsible sections](../jobs/index.md#custom-collapsible-sections) to simplify job log output. -### `secrets` **(PREMIUM)** +### `secrets` **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33014) in GitLab 13.4. diff --git a/doc/editor_extensions/gitlab_cli/index.md b/doc/editor_extensions/gitlab_cli/index.md index a16804d9f46..5f5bdfe091e 100644 --- a/doc/editor_extensions/gitlab_cli/index.md +++ b/doc/editor_extensions/gitlab_cli/index.md @@ -4,7 +4,7 @@ group: Code Review info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# GitLab CLI - `glab` **(FREE)** +# GitLab CLI - `glab` **(FREE ALL)** GLab is an open source GitLab CLI tool. It brings GitLab to your terminal: next to where you are already working with Git and your code, without diff --git a/doc/integration/jira/issues.md b/doc/integration/jira/issues.md index 448ae322fef..06d64d19db5 100644 --- a/doc/integration/jira/issues.md +++ b/doc/integration/jira/issues.md @@ -129,7 +129,7 @@ Consider this example: - GitLab adds a formatted comment to Jira, linking back to the commit that resolved the issue. You can [disable comments](#disable-comments-on-jira-issues). -## View Jira issues **(PREMIUM)** +## View Jira issues **(PREMIUM ALL)** You can view and search issues from a selected Jira project directly in GitLab, provided your GitLab administrator [has configured the integration](configure.md#configure-the-integration). @@ -152,7 +152,7 @@ Issues are grouped into tabs based on their - **Closed** tab: All issues with a Jira status categorized as Done. - **All** tab: All issues of any status. -### Search and filter the issue list **(PREMIUM)** +### Search and filter the issue list **(PREMIUM ALL)** To refine the list of issues, use the search bar to search for any text contained in an issue summary (title) or description. Use any combination diff --git a/doc/operations/feature_flags.md b/doc/operations/feature_flags.md index f4eb4281bed..21470f66750 100644 --- a/doc/operations/feature_flags.md +++ b/doc/operations/feature_flags.md @@ -216,7 +216,7 @@ To remove users from a user list: 1. Select **Edit** (**{pencil}**) next to the list you want to change. 1. Select **Remove** (**{remove}**) next to the ID you want to remove. -## Search for Code References **(PREMIUM)** +## Search for Code References **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/300299) in GitLab 14.4. @@ -397,7 +397,7 @@ docker run \ There is a limitation when using the Unleash Proxy where each proxy instance can request flags only for the environment named in `UNLEASH_APP_NAME`. The Proxy sends this to GitLab on behalf of the client, which means the client can't override it. -## Feature flag related issues **(PREMIUM)** +## Feature flag related issues **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/36617) in GitLab 13.2. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/251234) in GitLab 13.5. diff --git a/doc/operations/incident_management/alerts.md b/doc/operations/incident_management/alerts.md index 875ec26187b..e558462cad7 100644 --- a/doc/operations/incident_management/alerts.md +++ b/doc/operations/incident_management/alerts.md @@ -153,7 +153,7 @@ When you [close an incident](manage_incidents.md#close-an-incident) that is link GitLab [changes the alert's status](#change-an-alerts-status) to **Resolved**. You are then credited with the alert's status change. -#### As an on-call responder **(PREMIUM)** +#### As an on-call responder **(PREMIUM ALL)** On-call responders can respond to [alert pages](paging.md#escalating-an-alert) by changing the alert status. diff --git a/doc/operations/incident_management/escalation_policies.md b/doc/operations/incident_management/escalation_policies.md index 4360fe6243d..0cbbf42372e 100644 --- a/doc/operations/incident_management/escalation_policies.md +++ b/doc/operations/incident_management/escalation_policies.md @@ -4,7 +4,7 @@ group: Respond info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Escalation Policies **(PREMIUM)** +# Escalation Policies **(PREMIUM ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4638) in GitLab 14.1. diff --git a/doc/operations/incident_management/incidents.md b/doc/operations/incident_management/incidents.md index 0b91500b3bd..4aae8809620 100644 --- a/doc/operations/incident_management/incidents.md +++ b/doc/operations/incident_management/incidents.md @@ -97,7 +97,7 @@ Comments are displayed in threads, but can be displayed chronologically When you make changes to an incident, GitLab creates [system notes](../../user/project/system_notes.md) and displays them below the summary. -### Metrics **(PREMIUM)** +### Metrics **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/235994) in GitLab 13.8. @@ -130,7 +130,7 @@ during an incident, and the steps that were taken for it to be resolved. Read more about [timeline events](incident_timeline_events.md) and how to enable this feature. -### Recent updates view **(PREMIUM)** +### Recent updates view **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/227836) in GitLab 13.5. @@ -138,7 +138,7 @@ To see the latest updates on an incident, select **Turn recent updates view on** (**{history}**) on the comment bar. Comments display un-threaded and chronologically, newest to oldest. -### Service Level Agreement countdown timer **(PREMIUM)** +### Service Level Agreement countdown timer **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241663) in GitLab 13.5. diff --git a/doc/operations/incident_management/integrations.md b/doc/operations/incident_management/integrations.md index 220ca08a40a..5eed1921168 100644 --- a/doc/operations/incident_management/integrations.md +++ b/doc/operations/incident_management/integrations.md @@ -42,7 +42,7 @@ receive alert payloads in JSON format. You can always are available in the **View credentials** tab after you save the integration. You must also input the URL and Authorization Key in your external service. -### HTTP Endpoints **(PREMIUM)** +### HTTP Endpoints **(PREMIUM ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4442) in GitLab 13.6. @@ -395,7 +395,7 @@ alert to confirm your integration works properly. GitLab displays an error or success message, depending on the outcome of your test. -## Automatic grouping of identical alerts **(PREMIUM)** +## Automatic grouping of identical alerts **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/214557) in GitLab 13.2. @@ -420,7 +420,7 @@ field is `end_time`. With custom mappings, you can select the expected field. You can also configure the associated [incident to be closed automatically](../incident_management/manage_incidents.md#automatically-close-incidents-via-recovery-alerts) when the alert resolves. -## Link to your Opsgenie Alerts **(PREMIUM)** +## Link to your Opsgenie Alerts **(PREMIUM ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3066) in GitLab 13.2. diff --git a/doc/operations/incident_management/linked_resources.md b/doc/operations/incident_management/linked_resources.md index e43b08dfd78..15317f61057 100644 --- a/doc/operations/incident_management/linked_resources.md +++ b/doc/operations/incident_management/linked_resources.md @@ -4,7 +4,7 @@ group: Respond info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Linked resources in incidents **(PREMIUM)** +# Linked resources in incidents **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/230852) in GitLab 15.3 [with a flag](../../administration/feature_flags.md) named `incident_resource_links_widget`. Disabled by default. > - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/364755) in GitLab 15.3. diff --git a/doc/operations/incident_management/manage_incidents.md b/doc/operations/incident_management/manage_incidents.md index aca9123cef4..f88d9b51891 100644 --- a/doc/operations/incident_management/manage_incidents.md +++ b/doc/operations/incident_management/manage_incidents.md @@ -166,7 +166,7 @@ To change the status of an incident: **Triggered** is the default status for new incidents. -### As an on-call responder **(PREMIUM)** +### As an on-call responder **(PREMIUM ALL)** On-call responders can respond to [incident pages](paging.md#escalating-an-incident) by changing the status. @@ -181,7 +181,7 @@ In GitLab 15.1 and earlier, changing the status of an [incident created from an also changes the alert status. In [GitLab 15.2 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/356057), the alert status is independent and does not change when the incident status changes. -## Change escalation policy **(PREMIUM)** +## Change escalation policy **(PREMIUM ALL)** Prerequisites: diff --git a/doc/operations/incident_management/oncall_schedules.md b/doc/operations/incident_management/oncall_schedules.md index 8e3318766b4..808dc30581d 100644 --- a/doc/operations/incident_management/oncall_schedules.md +++ b/doc/operations/incident_management/oncall_schedules.md @@ -4,7 +4,7 @@ group: Respond info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# On-call Schedule Management **(PREMIUM)** +# On-call Schedule Management **(PREMIUM ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4544) in GitLab 13.11. diff --git a/doc/operations/incident_management/paging.md b/doc/operations/incident_management/paging.md index 3eec7a58361..05cc8c8e221 100644 --- a/doc/operations/incident_management/paging.md +++ b/doc/operations/incident_management/paging.md @@ -35,7 +35,7 @@ a single email notification for new alerts. [Update the alert's status](alerts.md#change-an-alerts-status) to manage email notifications for an alert. -## Paging **(PREMIUM)** +## Paging **(PREMIUM ALL)** In projects that have an [escalation policy](escalation_policies.md) configured, on-call responders can be automatically paged about critical problems through email. diff --git a/doc/policy/experiment-beta-support.md b/doc/policy/experiment-beta-support.md index b6156f9c20f..68cc96f118b 100644 --- a/doc/policy/experiment-beta-support.md +++ b/doc/policy/experiment-beta-support.md @@ -4,7 +4,7 @@ group: Distribution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Support for Experiment, Beta, and Generally Available features **(PREMIUM)** +# Support for Experiment, Beta, and Generally Available features **(PREMIUM ALL)** Some GitLab features are released as Experiment or Beta versions and are [not fully supported](https://about.gitlab.com/support/statement-of-support/#alpha-beta-features). diff --git a/doc/security/two_factor_authentication.md b/doc/security/two_factor_authentication.md index 307d6eb7167..906bf4cd062 100644 --- a/doc/security/two_factor_authentication.md +++ b/doc/security/two_factor_authentication.md @@ -132,7 +132,7 @@ sudo gitlab-rake gitlab:two_factor:disable_for_all_users sudo -u git -H bundle exec rake gitlab:two_factor:disable_for_all_users RAILS_ENV=production ``` -## 2FA for Git over SSH operations **(PREMIUM)** +## 2FA for Git over SSH operations **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/270554) in GitLab 13.7. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/299088) from GitLab Free to GitLab Premium in 13.9. diff --git a/doc/subscriptions/index.md b/doc/subscriptions/index.md index 0b78704bb4d..8577fdb460d 100644 --- a/doc/subscriptions/index.md +++ b/doc/subscriptions/index.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: index, reference --- -# Subscribe to GitLab **(PREMIUM)** +# Subscribe to GitLab **(PREMIUM ALL)** Choose and manage the subscription that's right for you and your organization. diff --git a/doc/subscriptions/quarterly_reconciliation.md b/doc/subscriptions/quarterly_reconciliation.md index 16f1828f2c3..7e7cc93e284 100644 --- a/doc/subscriptions/quarterly_reconciliation.md +++ b/doc/subscriptions/quarterly_reconciliation.md @@ -4,7 +4,7 @@ group: Purchase info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Quarterly reconciliation and annual true-ups **(PREMIUM)** +# Quarterly reconciliation and annual true-ups **(PREMIUM ALL)** GitLab reviews your seat usage and sends you an invoice for any overages. This review can occur: diff --git a/doc/topics/autodevops/cicd_variables.md b/doc/topics/autodevops/cicd_variables.md index dff36727bf2..a5897e0b233 100644 --- a/doc/topics/autodevops/cicd_variables.md +++ b/doc/topics/autodevops/cicd_variables.md @@ -255,7 +255,7 @@ production, GitLab creates a `production_manual` job. You can also enable manual deployment in your [project settings](requirements.md#auto-devops-deployment-strategy). -## Deploy policy for canary environments **(PREMIUM)** +## Deploy policy for canary environments **(PREMIUM ALL)** You can use a [canary environment](../../user/project/canary_deployments.md) before deploying any changes to production. @@ -265,7 +265,7 @@ If you set `CANARY_ENABLED`, GitLab creates two [manual jobs](../../ci/pipelines - `canary` - Deploys the application to the canary environment. - `production_manual` - Deploys the application to production. -## Incremental rollout to production **(PREMIUM)** +## Incremental rollout to production **(PREMIUM ALL)** Use an incremental rollout to continuously deploy your application, starting with only a few pods. You can increase the number of pods @@ -310,7 +310,7 @@ With `INCREMENTAL_ROLLOUT_MODE` set to `manual` and with `STAGING_ENABLED`:  -## Timed incremental rollout to production **(PREMIUM)** +## Timed incremental rollout to production **(PREMIUM ALL)** Use a timed incremental rollout to continuously deploy your application, starting with only a few pods. diff --git a/doc/topics/autodevops/stages.md b/doc/topics/autodevops/stages.md index 3f8a001c933..8d89736b56d 100644 --- a/doc/topics/autodevops/stages.md +++ b/doc/topics/autodevops/stages.md @@ -340,7 +340,7 @@ You can disable DAST: - Only on feature branches by setting `REVIEW_DISABLED` variable to `"true"`. This also disables the Review App. -## Auto Browser Performance Testing **(PREMIUM)** +## Auto Browser Performance Testing **(PREMIUM ALL)** > Introduced in GitLab 10.4. @@ -361,7 +361,7 @@ file named `.gitlab-urls.txt` in the root directory, one file per line. For exam Any browser performance differences between the source and target branches are also [shown in the merge request widget](../../ci/testing/browser_performance_testing.md). -## Auto Load Performance Testing **(PREMIUM)** +## Auto Load Performance Testing **(PREMIUM ALL)** > Introduced in GitLab 13.2. diff --git a/doc/tutorials/boards_for_teams/index.md b/doc/tutorials/boards_for_teams/index.md index fd8a1fe92a9..c316e42d218 100644 --- a/doc/tutorials/boards_for_teams/index.md +++ b/doc/tutorials/boards_for_teams/index.md @@ -4,7 +4,7 @@ group: Project Management info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Tutorial: Set up issue boards for team hand-off **(PREMIUM)** +# Tutorial: Set up issue boards for team hand-off **(PREMIUM ALL)** <!-- vale gitlab.FutureTense = NO --> diff --git a/doc/tutorials/issue_triage/index.md b/doc/tutorials/issue_triage/index.md index 07791060dd6..38e4285c2ce 100644 --- a/doc/tutorials/issue_triage/index.md +++ b/doc/tutorials/issue_triage/index.md @@ -79,7 +79,7 @@ handbook published with [GitLab Pages](../../user/project/pages/index.md). <!-- Idea for expanding this tutorial: Add steps for [creating a wiki page](../../user/project/wiki/index.md#create-a-new-wiki-page). --> -## Create scoped labels **(PREMIUM)** +## Create scoped labels **(PREMIUM ALL)** Next, you'll create labels to add to issues to categorize them. diff --git a/doc/user/analytics/code_review_analytics.md b/doc/user/analytics/code_review_analytics.md index 646a85fc7a2..27d3e45803e 100644 --- a/doc/user/analytics/code_review_analytics.md +++ b/doc/user/analytics/code_review_analytics.md @@ -5,7 +5,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Code review analytics **(PREMIUM)** +# Code review analytics **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/user/analytics/issue_analytics.md b/doc/user/analytics/issue_analytics.md index aaf33f48df2..7caee947318 100644 --- a/doc/user/analytics/issue_analytics.md +++ b/doc/user/analytics/issue_analytics.md @@ -5,7 +5,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Issue analytics for projects **(PREMIUM)** +# Issue analytics for projects **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/196561) in GitLab 12.9. diff --git a/doc/user/analytics/merge_request_analytics.md b/doc/user/analytics/merge_request_analytics.md index eeaa8271749..998f56ac40a 100644 --- a/doc/user/analytics/merge_request_analytics.md +++ b/doc/user/analytics/merge_request_analytics.md @@ -5,7 +5,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Merge request analytics **(PREMIUM)** +# Merge request analytics **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/229045) in GitLab 13.3. > - Moved to GitLab Premium in 13.9. diff --git a/doc/user/analytics/productivity_analytics.md b/doc/user/analytics/productivity_analytics.md index f53b516dd0d..ea896f07204 100644 --- a/doc/user/analytics/productivity_analytics.md +++ b/doc/user/analytics/productivity_analytics.md @@ -4,7 +4,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Productivity analytics **(PREMIUM)** +# Productivity analytics **(PREMIUM ALL)** You can use productivity analytics to identify: diff --git a/doc/user/application_security/policies/scan-execution-policies.md b/doc/user/application_security/policies/scan-execution-policies.md index 6c0023d027c..945d35c89da 100644 --- a/doc/user/application_security/policies/scan-execution-policies.md +++ b/doc/user/application_security/policies/scan-execution-policies.md @@ -4,7 +4,7 @@ group: Security Policies info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Scan execution policies **(ULTIMATE)** +# Scan execution policies **(ULTIMATE ALL)** > - Group-level security policies [introduced](https://gitlab.com/groups/gitlab-org/-/epics/4425) in GitLab 15.2. > - Group-level security policies [enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/356258) in GitLab 15.4. diff --git a/doc/user/application_security/policies/scan-result-policies.md b/doc/user/application_security/policies/scan-result-policies.md index fabc0cb41f8..a1e4707a09d 100644 --- a/doc/user/application_security/policies/scan-result-policies.md +++ b/doc/user/application_security/policies/scan-result-policies.md @@ -4,7 +4,7 @@ group: Security Policies info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Scan result policies **(ULTIMATE)** +# Scan result policies **(ULTIMATE ALL)** > Group-level scan result policies [introduced](https://gitlab.com/groups/gitlab-org/-/epics/7622) in GitLab 15.6. diff --git a/doc/user/application_security/sast/customize_rulesets.md b/doc/user/application_security/sast/customize_rulesets.md index 6b3755bc32a..4ae8f1c4f8b 100644 --- a/doc/user/application_security/sast/customize_rulesets.md +++ b/doc/user/application_security/sast/customize_rulesets.md @@ -4,7 +4,7 @@ group: Static Analysis info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Customize rulesets **(ULTIMATE)** +# Customize rulesets **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/235382) in GitLab 13.5. > - [Added](https://gitlab.com/gitlab-org/gitlab/-/issues/339614) support for diff --git a/doc/user/application_security/sast/index.md b/doc/user/application_security/sast/index.md index e0c2a1a7a43..35ededdc58c 100644 --- a/doc/user/application_security/sast/index.md +++ b/doc/user/application_security/sast/index.md @@ -119,7 +119,7 @@ The following analyzers have multi-project support: Multi-project support in the Security Code Scan requires a Solution (`.sln`) file in the root of the repository. For details on the Solution format, see the Microsoft reference [Solution (`.sln`) file](https://learn.microsoft.com/en-us/visualstudio/extensibility/internals/solution-dot-sln-file?view=vs-2019). -## False positive detection **(ULTIMATE)** +## False positive detection **(ULTIMATE ALL)** > - Introduced for Ruby in GitLab 14.2. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/378622) for Go in GitLab 15.8. @@ -134,7 +134,7 @@ False positive detection is available in a subset of the [supported languages](#  -## Advanced vulnerability tracking **(ULTIMATE)** +## Advanced vulnerability tracking **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5144) in GitLab 14.2. @@ -266,7 +266,7 @@ When downloading, you always receive the most recent SAST artifact available. You can enable and configure SAST by using the UI, either with the default settings or with customizations. The method you can use depends on your GitLab license tier. -#### Configure SAST with customizations **(ULTIMATE)** +#### Configure SAST with customizations **(ULTIMATE ALL)** > [Removed](https://gitlab.com/gitlab-org/gitlab/-/issues/410013) individual SAST analyzers configuration options from the UI in GitLab 16.2. diff --git a/doc/user/application_security/secret_detection/automatic_response.md b/doc/user/application_security/secret_detection/automatic_response.md index 1945d5c6cb0..1a5ab913b29 100644 --- a/doc/user/application_security/secret_detection/automatic_response.md +++ b/doc/user/application_security/secret_detection/automatic_response.md @@ -4,7 +4,7 @@ group: Static Analysis info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Automatic response to leaked secrets **(ULTIMATE)** +# Automatic response to leaked secrets **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/4639) in GitLab 13.6. diff --git a/doc/user/application_security/secret_detection/index.md b/doc/user/application_security/secret_detection/index.md index 932245c5629..10e8356de16 100644 --- a/doc/user/application_security/secret_detection/index.md +++ b/doc/user/application_security/secret_detection/index.md @@ -335,7 +335,7 @@ pipeline. To enable full history Secret Detection, set the variable `SECRET_DETECTION_HISTORIC_SCAN` to `true` in your `.gitlab-ci.yml` file. -## Custom rulesets **(ULTIMATE)** +## Custom rulesets **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/211387) in GitLab 13.5. > - [Added](https://gitlab.com/gitlab-org/gitlab/-/issues/339614) support for passthrough chains. diff --git a/doc/user/application_security/security_dashboard/index.md b/doc/user/application_security/security_dashboard/index.md index e28c06236aa..b6d95e53227 100644 --- a/doc/user/application_security/security_dashboard/index.md +++ b/doc/user/application_security/security_dashboard/index.md @@ -5,7 +5,7 @@ group: Threat Insights info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# GitLab Security Dashboards and Security Center **(ULTIMATE)** +# GitLab Security Dashboards and Security Center **(ULTIMATE ALL)** You can use Security Dashboards to view trends about vulnerabilities detected by [security scanners](../index.md#application-coverage). diff --git a/doc/user/application_security/vulnerabilities/index.md b/doc/user/application_security/vulnerabilities/index.md index 1ab70dc29b0..d36e901ae7e 100644 --- a/doc/user/application_security/vulnerabilities/index.md +++ b/doc/user/application_security/vulnerabilities/index.md @@ -4,7 +4,7 @@ group: Threat Insights info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Vulnerability Page **(ULTIMATE)** +# Vulnerability Page **(ULTIMATE ALL)** Each vulnerability in a project has a vulnerability page containing details of the vulnerability, including: diff --git a/doc/user/application_security/vulnerabilities/severities.md b/doc/user/application_security/vulnerabilities/severities.md index 605fef39090..31946d414a2 100644 --- a/doc/user/application_security/vulnerabilities/severities.md +++ b/doc/user/application_security/vulnerabilities/severities.md @@ -5,7 +5,7 @@ group: Threat Insights info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Vulnerability severity levels **(ULTIMATE)** +# Vulnerability severity levels **(ULTIMATE ALL)** GitLab vulnerability analyzers attempt to return vulnerability severity level values whenever possible. The following is a list of available GitLab vulnerability severity levels, ranked from diff --git a/doc/user/application_security/vulnerability_report/index.md b/doc/user/application_security/vulnerability_report/index.md index 2f439588e2b..46ce3173ee7 100644 --- a/doc/user/application_security/vulnerability_report/index.md +++ b/doc/user/application_security/vulnerability_report/index.md @@ -5,7 +5,7 @@ group: Threat Insights info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Vulnerability Report **(ULTIMATE)** +# Vulnerability Report **(ULTIMATE ALL)** The Vulnerability Report provides information about vulnerabilities from scans of the default branch. It contains cumulative results of all successful jobs, regardless of whether the pipeline was successful. The scan results from a diff --git a/doc/user/clusters/agent/ci_cd_workflow.md b/doc/user/clusters/agent/ci_cd_workflow.md index 4dea3f1bb0d..260263632c5 100644 --- a/doc/user/clusters/agent/ci_cd_workflow.md +++ b/doc/user/clusters/agent/ci_cd_workflow.md @@ -196,7 +196,7 @@ To configure your client, do one of the following: - Place the certificates in an appropriate location in the job container by updating the container image or mounting via the runner. - Not recommended. Configure the Kubernetes client with `--insecure-skip-tls-verify=true`. -## Restrict project and group access by using impersonation **(PREMIUM)** +## Restrict project and group access by using impersonation **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/345014) in GitLab 14.5. > - [Changed](https://gitlab.com/gitlab-org/gitlab/-/issues/357934) in GitLab 15.5 to add impersonation support for environment tiers. diff --git a/doc/user/clusters/agent/user_access.md b/doc/user/clusters/agent/user_access.md index efb09361119..a5989d823f6 100644 --- a/doc/user/clusters/agent/user_access.md +++ b/doc/user/clusters/agent/user_access.md @@ -56,7 +56,7 @@ user_access: - id: group-3/subgroup ``` -## Configure access with user impersonation **(PREMIUM)** +## Configure access with user impersonation **(PREMIUM ALL)** You can grant access to a Kubernetes cluster and transform requests into impersonation requests for authenticated users. diff --git a/doc/user/clusters/agent/vulnerabilities.md b/doc/user/clusters/agent/vulnerabilities.md index 74676e31d22..a967ec9ea24 100644 --- a/doc/user/clusters/agent/vulnerabilities.md +++ b/doc/user/clusters/agent/vulnerabilities.md @@ -4,7 +4,7 @@ group: Composition analysis info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Operational Container Scanning **(ULTIMATE)** +# Operational Container Scanning **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/6346) in GitLab 14.8. > - [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/368828) the starboard directive in GitLab 15.4. The starboard directive is scheduled for removal in GitLab 16.0. diff --git a/doc/user/clusters/cost_management.md b/doc/user/clusters/cost_management.md index 6ed0f08c4a7..a155dcf4a3c 100644 --- a/doc/user/clusters/cost_management.md +++ b/doc/user/clusters/cost_management.md @@ -6,7 +6,7 @@ remove_date: '2023-08-22' redirect_to: '../index.md' --- -# Cluster cost management (removed) **(ULTIMATE)** +# Cluster cost management (removed) **(ULTIMATE ALL)** This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346541) in GitLab 14.7 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/399231) in 16.0. diff --git a/doc/user/clusters/environments.md b/doc/user/clusters/environments.md index fa56dc320be..4a6fa8d4862 100644 --- a/doc/user/clusters/environments.md +++ b/doc/user/clusters/environments.md @@ -4,7 +4,7 @@ group: Environments info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Cluster Environments (deprecated) **(PREMIUM)** +# Cluster Environments (deprecated) **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13392) in GitLab 12.3 for group-level clusters. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14809) in GitLab 12.4 for instance-level clusters. diff --git a/doc/user/compliance/compliance_center/index.md b/doc/user/compliance/compliance_center/index.md index e30edd09428..9660b722016 100644 --- a/doc/user/compliance/compliance_center/index.md +++ b/doc/user/compliance/compliance_center/index.md @@ -5,7 +5,7 @@ group: Compliance info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Compliance center **(ULTIMATE)** +# Compliance center **(ULTIMATE ALL)** > [Renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122931) from Compliance report in GitLab 16.3. diff --git a/doc/user/compliance/index.md b/doc/user/compliance/index.md index ae705b5edc6..51053c03d8c 100644 --- a/doc/user/compliance/index.md +++ b/doc/user/compliance/index.md @@ -5,7 +5,7 @@ group: Compliance info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Compliance **(ULTIMATE)** +# Compliance **(ULTIMATE ALL)** The compliance tools provided by GitLab help you keep an eye on various aspects of your project, including: diff --git a/doc/user/compliance/license_approval_policies.md b/doc/user/compliance/license_approval_policies.md index 96a4a08249a..e3350b1ae10 100644 --- a/doc/user/compliance/license_approval_policies.md +++ b/doc/user/compliance/license_approval_policies.md @@ -5,7 +5,7 @@ group: Security Policies info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# License approval policies **(ULTIMATE)** +# License approval policies **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/8092) in GitLab 15.9 [with a flag](../../administration/feature_flags.md) named `license_scanning_policies`. > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/397644) in GitLab 15.11. Feature flag `license_scanning_policies` removed. diff --git a/doc/user/compliance/license_compliance/index.md b/doc/user/compliance/license_compliance/index.md index fa6c2c1a6c1..00578219016 100644 --- a/doc/user/compliance/license_compliance/index.md +++ b/doc/user/compliance/license_compliance/index.md @@ -7,7 +7,7 @@ remove_date: '2023-08-22' redirect_to: '../license_approval_policies.md' --- -# License Compliance (removed) **(ULTIMATE)** +# License Compliance (removed) **(ULTIMATE ALL)** This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/387561) in GitLab 15.9 and [removed](https://gitlab.com/gitlab-org/gitlab/-/issues/421363) in GitLab 16.3. diff --git a/doc/user/compliance/license_list.md b/doc/user/compliance/license_list.md index 1105d22ecce..96ea43e5ce2 100644 --- a/doc/user/compliance/license_list.md +++ b/doc/user/compliance/license_list.md @@ -5,7 +5,7 @@ group: Threat Insights info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# License list **(ULTIMATE)** +# License list **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13582) in GitLab 12.7. diff --git a/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md b/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md index 4922720f905..22715bb5794 100644 --- a/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md +++ b/doc/user/compliance/license_scanning_of_cyclonedx_files/index.md @@ -5,7 +5,7 @@ group: Composition Analysis info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# License scanning of CycloneDX files **(ULTIMATE)** +# License scanning of CycloneDX files **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/384932) in GitLab 15.9 for GitLab SaaS [with two flags](../../../administration/feature_flags.md) named `license_scanning_sbom_scanner` and `package_metadata_synchronization`. Both flags are disabled by default and both flags must be enabled for this feature to work. > - [Enabled](https://gitlab.com/gitlab-org/gitlab/-/issues/385173) in GitLab 15.10 for GitLab SaaS. diff --git a/doc/user/discussions/index.md b/doc/user/discussions/index.md index 99b206fa6d1..0bdbfe79775 100644 --- a/doc/user/discussions/index.md +++ b/doc/user/discussions/index.md @@ -221,7 +221,7 @@ To change the activity sort order: 1. On the right side of the page, from the **Sort or filter** dropdown list, select the sort order **Newest first** or **Oldest first** (default). -## View description change history **(PREMIUM)** +## View description change history **(PREMIUM ALL)** You can see changes to the description listed in the history. diff --git a/doc/user/group/access_and_permissions.md b/doc/user/group/access_and_permissions.md index fa6130fe56d..0ccd4512039 100644 --- a/doc/user/group/access_and_permissions.md +++ b/doc/user/group/access_and_permissions.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w Configure your groups to control group permissions and access. -## Group push rules **(PREMIUM)** +## Group push rules **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/34370) in GitLab 12.8. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/224129) in GitLab 13.4. @@ -52,7 +52,7 @@ To change the permitted Git access protocols for a group: 1. Choose the permitted protocols from **Enabled Git access protocols**. 1. Select **Save changes**. -## Restrict group access by IP address **(PREMIUM)** +## Restrict group access by IP address **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1985) in GitLab 12.0. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/215410) from GitLab Ultimate to GitLab Premium in 13.1. @@ -103,7 +103,7 @@ Keep in mind that restricting group access by IP address has the following impli with [PROXY protocol](../../administration/operations/gitlab_sshd.md#proxy-protocol-support) enabled. - IP restriction is not applicable to shared resources belonging to a group. Any shared resource is accessible to a user even if that user is not able to access the group. -## Restrict group access by domain **(PREMIUM)** +## Restrict group access by domain **(PREMIUM ALL)** > - Support for specifying multiple email domains [added](https://gitlab.com/gitlab-org/gitlab/-/issues/33143) in GitLab 13.1. > - Support for restricting access to projects in the group [added](https://gitlab.com/gitlab-org/gitlab/-/issues/14004) in GitLab 14.1.2. @@ -193,7 +193,7 @@ your group. 1. Clear the **Allow users to request access** checkbox. 1. Select **Save changes**. -## Prevent project forking outside group **(PREMIUM)** +## Prevent project forking outside group **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216987) in GitLab 13.3. @@ -215,7 +215,7 @@ To prevent projects from being forked outside the group: Existing forks are not removed. -## Prevent members from being added to projects in a group **(PREMIUM)** +## Prevent members from being added to projects in a group **(PREMIUM ALL)** As a group Owner, you can prevent any new project membership for all projects in a group, allowing tighter control over project membership. diff --git a/doc/user/group/clusters/index.md b/doc/user/group/clusters/index.md index 979a3bb51c4..e41991f365c 100644 --- a/doc/user/group/clusters/index.md +++ b/doc/user/group/clusters/index.md @@ -106,7 +106,7 @@ the [Auto DevOps](../../../topics/autodevops/index.md) stages. The domain should have a wildcard DNS configured to the Ingress IP address. [More details](../../project/clusters/gitlab_managed_clusters.md#base-domain). -## Environment scopes **(PREMIUM)** +## Environment scopes **(PREMIUM ALL)** When adding more than one Kubernetes cluster to your project, you need to differentiate them with an environment scope. The environment scope associates clusters with @@ -162,7 +162,7 @@ The result is: - The Staging cluster is used for the `deploy to staging` job. - The Production cluster is used for the `deploy to production` job. -## Cluster environments **(PREMIUM)** +## Cluster environments **(PREMIUM ALL)** For a consolidated view of which CI [environments](../../../ci/environments/index.md) are deployed to the Kubernetes cluster, see the documentation for diff --git a/doc/user/group/compliance_frameworks.md b/doc/user/group/compliance_frameworks.md index 267cdbbebd3..35e8ad27bc3 100644 --- a/doc/user/group/compliance_frameworks.md +++ b/doc/user/group/compliance_frameworks.md @@ -4,7 +4,7 @@ group: Compliance info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Compliance frameworks **(PREMIUM)** +# Compliance frameworks **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/276221) in GitLab 13.9. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/287779) in GitLab 13.12. @@ -113,7 +113,7 @@ mutation { } ``` -## Compliance pipelines **(ULTIMATE)** +## Compliance pipelines **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3156) in GitLab 13.9, disabled behind `ff_evaluate_group_level_compliance_pipeline` [feature flag](../../administration/feature_flags.md). > - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/300324) in GitLab 13.11. diff --git a/doc/user/group/contribution_analytics/index.md b/doc/user/group/contribution_analytics/index.md index 02f1e7f21e2..9716143f5e2 100644 --- a/doc/user/group/contribution_analytics/index.md +++ b/doc/user/group/contribution_analytics/index.md @@ -4,7 +4,7 @@ stage: Plan group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Contribution analytics **(PREMIUM)** +# Contribution analytics **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/3090) in GitLab 12.2 for subgroups. diff --git a/doc/user/group/custom_project_templates.md b/doc/user/group/custom_project_templates.md index 61056296054..1a481641111 100644 --- a/doc/user/group/custom_project_templates.md +++ b/doc/user/group/custom_project_templates.md @@ -4,7 +4,7 @@ group: Source Code info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Custom group-level project templates **(PREMIUM)** +# Custom group-level project templates **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/6861) in GitLab 11.6. diff --git a/doc/user/group/devops_adoption/index.md b/doc/user/group/devops_adoption/index.md index 7aa4695e58b..852d26f3816 100644 --- a/doc/user/group/devops_adoption/index.md +++ b/doc/user/group/devops_adoption/index.md @@ -4,7 +4,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Group DevOps Adoption **(ULTIMATE)** +# Group DevOps Adoption **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/321083) in GitLab 13.11 as a [Beta feature](../../../policy/experiment-beta-support.md#beta). > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/333556) in GitLab 14.1. diff --git a/doc/user/group/epics/index.md b/doc/user/group/epics/index.md index 5d3bac4f895..7b977dc2026 100644 --- a/doc/user/group/epics/index.md +++ b/doc/user/group/epics/index.md @@ -4,7 +4,7 @@ group: Product Planning info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Epics **(PREMIUM)** +# Epics **(PREMIUM ALL)** When [issues](../../project/issues/index.md) share a theme across projects and milestones, you can manage them by using epics. @@ -52,7 +52,7 @@ You can add issues from a different group hierarchy to an epic. To do it, paste the issue URL when [adding an existing issue](manage_epics.md#add-an-existing-issue-to-an-epic). -## Roadmap in epics **(ULTIMATE)** +## Roadmap in epics **(ULTIMATE ALL)** If your epic contains one or more [child epics](manage_epics.md#multi-level-child-epics) that have a start or due date, a visual diff --git a/doc/user/group/epics/linked_epics.md b/doc/user/group/epics/linked_epics.md index 9ce4a585d14..8b57c1b4d1f 100644 --- a/doc/user/group/epics/linked_epics.md +++ b/doc/user/group/epics/linked_epics.md @@ -4,7 +4,7 @@ group: Product Planning info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Linked epics **(ULTIMATE)** +# Linked epics **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/353473) in GitLab 14.9 [with a flag](../../../administration/feature_flags.md) named `related_epics_widget`. Enabled by default. > - [Feature flag `related_epics_widget`](https://gitlab.com/gitlab-org/gitlab/-/issues/357089) removed in GitLab 15.0. diff --git a/doc/user/group/epics/manage_epics.md b/doc/user/group/epics/manage_epics.md index 8265540cc34..b30ed0344b2 100644 --- a/doc/user/group/epics/manage_epics.md +++ b/doc/user/group/epics/manage_epics.md @@ -448,7 +448,7 @@ To reorder issues assigned to an epic: 1. Go to the **Child issues and epics** section. 1. Drag issues into the desired order. -### Move issues between epics **(ULTIMATE)** +### Move issues between epics **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/33039) in GitLab 13.0. > - Minimum required role for the project [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/382506) from Reporter to Guest in GitLab 15.8. @@ -508,7 +508,7 @@ For an introduction to epic templates, see [GitLab Epics and Epic Template Tip]( For more on epic templates, see [Epic Templates - Repeatable sets of issues](https://about.gitlab.com/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/getting-started/104/). -## Multi-level child epics **(ULTIMATE)** +## Multi-level child epics **(ULTIMATE ALL)** You can add any epic that belongs to a group or subgroup of the parent epic's group. New child epics appear at the top of the list of epics in the **Child issues and epics** section. diff --git a/doc/user/group/index.md b/doc/user/group/index.md index 84674d5ef2e..13fba43f8ef 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -129,7 +129,7 @@ In [GitLab 12.8 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/33257), In [GitLab 13.6 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/39504), if the user who sets up the deletion is removed from the group before the deletion happens, the job is cancelled, and the group is no longer scheduled for deletion. -## Remove a group immediately **(PREMIUM)** +## Remove a group immediately **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/336985) in GitLab 14.2. > - Enabled delayed deletion by default and removed the option to delete immediately [on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/393622) and [on self-managed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/119606) in GitLab 16.0. @@ -152,7 +152,7 @@ To immediately remove a group marked for deletion: Your group, its subgroups, projects, and all related resources, including issues and merge requests, are deleted. -## Restore a group **(PREMIUM)** +## Restore a group **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/33257) in GitLab 12.8. diff --git a/doc/user/group/insights/index.md b/doc/user/group/insights/index.md index 61ec055c6ee..5cb982a85e4 100644 --- a/doc/user/group/insights/index.md +++ b/doc/user/group/insights/index.md @@ -4,7 +4,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Insights for groups **(ULTIMATE)** +# Insights for groups **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/725) in GitLab 12.0. diff --git a/doc/user/group/planning_hierarchy/index.md b/doc/user/group/planning_hierarchy/index.md index f48a027ab2d..2dc8c94a16a 100644 --- a/doc/user/group/planning_hierarchy/index.md +++ b/doc/user/group/planning_hierarchy/index.md @@ -31,7 +31,7 @@ graph TD Group_epic --> Project2_Issue1 ``` -### Hierarchies with multi-level epics **(ULTIMATE)** +### Hierarchies with multi-level epics **(ULTIMATE ALL)** With the addition of [multi-level epics](../epics/manage_epics.md#multi-level-child-epics) and up to seven levels of nested epics, you can achieve the following hierarchy: diff --git a/doc/user/group/reporting/git_abuse_rate_limit.md b/doc/user/group/reporting/git_abuse_rate_limit.md index cde19531ed3..abb967ad8b1 100644 --- a/doc/user/group/reporting/git_abuse_rate_limit.md +++ b/doc/user/group/reporting/git_abuse_rate_limit.md @@ -4,7 +4,7 @@ group: Anti-Abuse info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Git abuse rate limit **(ULTIMATE)** +# Git abuse rate limit **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/8066) in GitLab 15.2 [with a flag](../../../administration/feature_flags.md) named `limit_unique_project_downloads_per_namespace_user`. Disabled by default. diff --git a/doc/user/group/roadmap/index.md b/doc/user/group/roadmap/index.md index 9e0ff22eafa..a34e1e7d2af 100644 --- a/doc/user/group/roadmap/index.md +++ b/doc/user/group/roadmap/index.md @@ -150,7 +150,7 @@ the timeline header represent the days of the week. The timeline bar indicates the approximate position of an epic or milestone based on its start and due dates. -## Blocked epics **(ULTIMATE)** +## Blocked epics **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/33587) in GitLab 15.5: View blocking epics when hovering over the "blocked" icon. diff --git a/doc/user/group/value_stream_analytics/index.md b/doc/user/group/value_stream_analytics/index.md index b110750e5b9..79c9e2e1680 100644 --- a/doc/user/group/value_stream_analytics/index.md +++ b/doc/user/group/value_stream_analytics/index.md @@ -267,7 +267,7 @@ Value stream analytics includes the following lifecycle metrics: - **New issues**: Number of new issues created. - **Deploys**: Total number of deployments to production. -### DORA metrics **(ULTIMATE)** +### DORA metrics **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/340150) lead time for changes DORA metric in GitLab 14.5. > - DORA API-based deployment metrics for value stream analytics for groups were [moved](https://gitlab.com/gitlab-org/gitlab/-/issues/337256) from GitLab Ultimate to GitLab Premium in GitLab 14.3. diff --git a/doc/user/permissions.md b/doc/user/permissions.md index 26eec6e3c92..d19f98b98ed 100644 --- a/doc/user/permissions.md +++ b/doc/user/permissions.md @@ -429,7 +429,7 @@ nested groups if you have membership in one of its parents. For more information, see [subgroup memberships](group/subgroups/index.md#subgroup-membership). -## Users with Minimal Access **(PREMIUM)** +## Users with Minimal Access **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/40942) in GitLab 13.4. > - Support for inviting users with Minimal Access role [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/106438) in GitLab 15.9. diff --git a/doc/user/product_analytics/index.md b/doc/user/product_analytics/index.md index c2aefb3eead..06a90af55c7 100644 --- a/doc/user/product_analytics/index.md +++ b/doc/user/product_analytics/index.md @@ -4,7 +4,7 @@ group: Product Analytics info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Product analytics (Experiment) **(ULTIMATE)** +# Product analytics (Experiment) **(ULTIMATE ALL)** > - Introduced in GitLab 15.4 as an [Experiment](../../policy/experiment-beta-support.md#experiment) feature [with a flag](../../administration/feature_flags.md) named `cube_api_proxy`. Disabled by default. > - `cube_api_proxy` revised to only reference the [Product Analytics API](../../api/product_analytics.md) in GitLab 15.6. diff --git a/doc/user/project/index.md b/doc/user/project/index.md index 16e17191665..a9914f7b2a9 100644 --- a/doc/user/project/index.md +++ b/doc/user/project/index.md @@ -87,7 +87,7 @@ Custom project templates are available at: change the **Visibility Level**. 1. Select **Create project**. -## Create a project from the HIPAA Audit Protocol template **(ULTIMATE)** +## Create a project from the HIPAA Audit Protocol template **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13756) in GitLab 12.10 diff --git a/doc/user/project/insights/index.md b/doc/user/project/insights/index.md index 533824dd58a..60b23540ac3 100644 --- a/doc/user/project/insights/index.md +++ b/doc/user/project/insights/index.md @@ -4,7 +4,7 @@ group: Optimize info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Insights for projects **(ULTIMATE)** +# Insights for projects **(ULTIMATE ALL)** Configure project insights to explore data such as: diff --git a/doc/user/project/issues/managing_issues.md b/doc/user/project/issues/managing_issues.md index 80669eba140..3ee6029d2f3 100644 --- a/doc/user/project/issues/managing_issues.md +++ b/doc/user/project/issues/managing_issues.md @@ -566,7 +566,7 @@ As you type in the title text box of the **New issue** page, GitLab searches tit across all issues in the current project. Only issues you have access to are returned. Up to five similar issues, sorted by most recently updated, are displayed below the title text box. -## Health status **(ULTIMATE)** +## Health status **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/36427) in GitLab 12.10. > - Health status of closed issues [can't be edited](https://gitlab.com/gitlab-org/gitlab/-/issues/220867) in GitLab 13.4 and later. @@ -607,7 +607,7 @@ until the issue is reopened. You can also set and clear health statuses using the `/health_status` and `/clear_health_status` [quick actions](../quick_actions.md#issues-merge-requests-and-epics). -## Publish an issue **(ULTIMATE)** +## Publish an issue **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/30906) in GitLab 13.1. diff --git a/doc/user/project/issues/related_issues.md b/doc/user/project/issues/related_issues.md index 029558d1b2d..10c7899ac30 100644 --- a/doc/user/project/issues/related_issues.md +++ b/doc/user/project/issues/related_issues.md @@ -70,7 +70,7 @@ Due to the bi-directional relationship, the relationship no longer appears in ei Access our [permissions](../../permissions.md) page for more information. -## Blocking issues **(PREMIUM)** +## Blocking issues **(PREMIUM ALL)** When you [add a linked issue](#add-a-linked-issue), you can show that it **blocks** or **is blocked by** another issue. diff --git a/doc/user/project/issues/sorting_issue_lists.md b/doc/user/project/issues/sorting_issue_lists.md index f4daf39d81a..c365bfa5a52 100644 --- a/doc/user/project/issues/sorting_issue_lists.md +++ b/doc/user/project/issues/sorting_issue_lists.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w You can sort a list of issues several ways. The available sorting options can change based on the context of the list. -## Sorting by blocking issues **(PREMIUM)** +## Sorting by blocking issues **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/34247/) in GitLab 13.7. @@ -105,7 +105,7 @@ title in this order: - Numbers - Letters: first Latin, then accented (for example, `ö`) -## Sorting by health status **(ULTIMATE)** +## Sorting by health status **(ULTIMATE ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/377841) in GitLab 15.7. diff --git a/doc/user/project/merge_requests/approvals/index.md b/doc/user/project/merge_requests/approvals/index.md index c91890b68db..bace1dfb8b5 100644 --- a/doc/user/project/merge_requests/approvals/index.md +++ b/doc/user/project/merge_requests/approvals/index.md @@ -87,7 +87,7 @@ GitLab allows all users with Developer or greater [permissions](../../../permiss to approve merge requests. Approvals in GitLab Free are optional, and don't prevent a merge request from merging without approval. -## Required approvals **(PREMIUM)** +## Required approvals **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/user/project/merge_requests/approvals/rules.md b/doc/user/project/merge_requests/approvals/rules.md index cc931d8cb13..cbbeac17355 100644 --- a/doc/user/project/merge_requests/approvals/rules.md +++ b/doc/user/project/merge_requests/approvals/rules.md @@ -4,7 +4,7 @@ group: Source Code info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Merge request approval rules **(PREMIUM)** +# Merge request approval rules **(PREMIUM ALL)** Approval rules define how many [approvals](index.md) a merge request must receive before it can be merged, and which users should do the approving. They can be used in conjunction diff --git a/doc/user/project/merge_requests/approvals/settings.md b/doc/user/project/merge_requests/approvals/settings.md index db0580f4bab..b520ee41493 100644 --- a/doc/user/project/merge_requests/approvals/settings.md +++ b/doc/user/project/merge_requests/approvals/settings.md @@ -4,7 +4,7 @@ group: Source Code info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Merge request approval settings **(PREMIUM)** +# Merge request approval settings **(PREMIUM ALL)** You can configure the settings for [merge request approvals](index.md) to ensure the approval rules meet your use case. You can also configure diff --git a/doc/user/project/merge_requests/dependencies.md b/doc/user/project/merge_requests/dependencies.md index 1cd81e2aac2..b80698f99c3 100644 --- a/doc/user/project/merge_requests/dependencies.md +++ b/doc/user/project/merge_requests/dependencies.md @@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w type: reference, concepts --- -# Merge request dependencies **(PREMIUM)** +# Merge request dependencies **(PREMIUM ALL)** A single feature can span several merge requests, spread out across multiple projects, and the order in which the work merges can be significant. Use merge request dependencies diff --git a/doc/user/project/merge_requests/reviews/index.md b/doc/user/project/merge_requests/reviews/index.md index da1fc687b96..e4882134654 100644 --- a/doc/user/project/merge_requests/reviews/index.md +++ b/doc/user/project/merge_requests/reviews/index.md @@ -159,7 +159,7 @@ If you have a review in progress, you can also add a comment from the **Overview  -### Approval Rule information for Reviewers **(PREMIUM)** +### Approval Rule information for Reviewers **(PREMIUM ALL)** When editing the **Reviewers** field in a new or existing merge request, GitLab displays the name of the matching [approval rule](../approvals/rules.md) @@ -225,7 +225,7 @@ To update multiple project merge requests at the same time: 1. Select the appropriate fields and their values from the sidebar. 1. Select **Update all**. -## Bulk edit merge requests at the group level **(PREMIUM)** +## Bulk edit merge requests at the group level **(PREMIUM ALL)** Users with at least the Developer role can manage merge requests. diff --git a/doc/user/project/merge_requests/status_checks.md b/doc/user/project/merge_requests/status_checks.md index a151a7cbf1b..e0e65c99433 100644 --- a/doc/user/project/merge_requests/status_checks.md +++ b/doc/user/project/merge_requests/status_checks.md @@ -5,7 +5,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated type: reference, concepts --- -# External status checks **(ULTIMATE)** +# External status checks **(ULTIMATE ALL)** > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3869) in GitLab 14.0, disabled behind the `:ff_external_status_checks` feature flag. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/320783) in GitLab 14.1. diff --git a/doc/user/project/milestones/burndown_and_burnup_charts.md b/doc/user/project/milestones/burndown_and_burnup_charts.md index 59b11e78622..7c9a5a37292 100644 --- a/doc/user/project/milestones/burndown_and_burnup_charts.md +++ b/doc/user/project/milestones/burndown_and_burnup_charts.md @@ -5,7 +5,7 @@ group: Project Management info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Burndown and burnup charts **(PREMIUM)** +# Burndown and burnup charts **(PREMIUM ALL)** [Burndown](#burndown-charts) and [burnup](#burnup-charts) charts show the progress of completing a milestone. diff --git a/doc/user/project/remote_development/index.md b/doc/user/project/remote_development/index.md index 297d32866db..16110af984a 100644 --- a/doc/user/project/remote_development/index.md +++ b/doc/user/project/remote_development/index.md @@ -36,7 +36,7 @@ With remote development, you can use: For a complete IDE experience, connect the Web IDE to a development environment configured to run as a remote host. You can create this environment [inside](../../workspace/configuration.md) or [outside](connect_machine.md) of GitLab. -## Workspaces **(PREMIUM)** +## Workspaces **(PREMIUM ALL)** A [workspace](../../workspace/index.md) is a virtual sandbox environment for your code in GitLab that includes: diff --git a/doc/user/project/repository/branches/default.md b/doc/user/project/repository/branches/default.md index 4913e560962..e123debb724 100644 --- a/doc/user/project/repository/branches/default.md +++ b/doc/user/project/repository/branches/default.md @@ -156,7 +156,7 @@ disable this privilege for group owners, enforcing the instance-level protection NOTE: GitLab administrators can still update the default branch protection of a group. -### Group-level default branch protection **(PREMIUM)** +### Group-level default branch protection **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7583) in GitLab 12.9. > - [Settings moved and renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/340403) in GitLab 14.9. diff --git a/doc/user/project/repository/forking_workflow.md b/doc/user/project/repository/forking_workflow.md index 64b3fd2d937..4c37b92b388 100644 --- a/doc/user/project/repository/forking_workflow.md +++ b/doc/user/project/repository/forking_workflow.md @@ -134,7 +134,7 @@ an `upstream` remote repository for your fork: git push origin main ``` -### With repository mirroring **(PREMIUM)** +### With repository mirroring **(PREMIUM ALL)** A fork can be configured as a mirror of the upstream if all these conditions are met: diff --git a/doc/user/project/repository/mirror/bidirectional.md b/doc/user/project/repository/mirror/bidirectional.md index d06d9ba0c54..fade9e1b63c 100644 --- a/doc/user/project/repository/mirror/bidirectional.md +++ b/doc/user/project/repository/mirror/bidirectional.md @@ -4,7 +4,7 @@ group: Source Code info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Bidirectional mirroring **(PREMIUM)** +# Bidirectional mirroring **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. @@ -138,7 +138,7 @@ This sample has a few limitations: - The script circumvents the Git hook quarantine environment because the update of `$TARGET_REPO` is seen as a ref update, and Git displays warnings about it. -## Mirror with Perforce Helix with Git Fusion **(PREMIUM)** +## Mirror with Perforce Helix with Git Fusion **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/user/project/repository/mirror/index.md b/doc/user/project/repository/mirror/index.md index 711349ebf3a..7ade27e556d 100644 --- a/doc/user/project/repository/mirror/index.md +++ b/doc/user/project/repository/mirror/index.md @@ -77,7 +77,7 @@ non-protected branches in the mirroring project are not mirrored and can diverge To use this option, select **Only mirror protected branches** when you create a repository mirror. -### Mirror specific branches **(PREMIUM)** +### Mirror specific branches **(PREMIUM ALL)** > - Mirroring branches matching a regex [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/102608) in GitLab 15.8 [with a flag](../../../../administration/feature_flags.md) named `mirror_only_branches_match_regex`. Disabled by default. > - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/381667) in GitLab 16.0. diff --git a/doc/user/project/repository/mirror/pull.md b/doc/user/project/repository/mirror/pull.md index 5795f1db732..ba54c18f8ee 100644 --- a/doc/user/project/repository/mirror/pull.md +++ b/doc/user/project/repository/mirror/pull.md @@ -4,7 +4,7 @@ group: Source Code info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Pull from a remote repository **(PREMIUM)** +# Pull from a remote repository **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/user/project/repository/push_rules.md b/doc/user/project/repository/push_rules.md index 31257ee7811..2756149b5bd 100644 --- a/doc/user/project/repository/push_rules.md +++ b/doc/user/project/repository/push_rules.md @@ -4,7 +4,7 @@ group: Source Code info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments" --- -# Push rules **(PREMIUM)** +# Push rules **(PREMIUM ALL)** > Maximum regular expression length for push rules [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/411901) from 255 to 511 characters in GitLab 16.3. diff --git a/doc/user/project/repository/tags/index.md b/doc/user/project/repository/tags/index.md index 93988fb0e6c..5a01d6f2085 100644 --- a/doc/user/project/repository/tags/index.md +++ b/doc/user/project/repository/tags/index.md @@ -97,7 +97,7 @@ To create a tag from the GitLab UI: create a lightweight tag. 1. Select **Create tag**. -## Prevent tag deletion **(PREMIUM)** +## Prevent tag deletion **(PREMIUM ALL)** To prevent users from removing a tag with `git push`, create a [push rule](../push_rules.md). diff --git a/doc/user/project/settings/index.md b/doc/user/project/settings/index.md index d00da8dde35..6c2140595d9 100644 --- a/doc/user/project/settings/index.md +++ b/doc/user/project/settings/index.md @@ -46,7 +46,7 @@ If you're an instance administrator, you can administer all project topics from NOTE: The assigned topics are visible only to users with access to the project, but everyone can see which topics exist on the GitLab instance. Do not include sensitive information in the name of a topic. -## Add a compliance framework to a project **(PREMIUM)** +## Add a compliance framework to a project **(PREMIUM ALL)** You can [add compliance frameworks to projects](../../group/compliance_frameworks.md#add-a-compliance-framework-to-a-project) @@ -312,7 +312,7 @@ To delete a project: This action deletes the project and all associated resources (such as issues and merge requests). -### Delayed project deletion **(PREMIUM)** +### Delayed project deletion **(PREMIUM ALL)** > - [Enabled for projects in personal namespaces](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89466) in GitLab 15.1. > - [Disabled for projects in personal namespaces](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/95495) in GitLab 15.3. @@ -346,7 +346,7 @@ To immediately delete a project marked for deletion: 1. In the **Delete this project** section, select **Delete project**. 1. On the confirmation dialog, enter the project name and select **Yes, delete project**. -## Restore a project **(PREMIUM)** +## Restore a project **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/32935) in GitLab 12.6. diff --git a/doc/user/project/wiki/group.md b/doc/user/project/wiki/group.md index 41fd7e81db5..916c8abf066 100644 --- a/doc/user/project/wiki/group.md +++ b/doc/user/project/wiki/group.md @@ -4,7 +4,7 @@ group: Knowledge info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Group wikis **(PREMIUM)** +# Group wikis **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/13195) in GitLab 13.5. diff --git a/doc/user/search/advanced_search.md b/doc/user/search/advanced_search.md index 9b398194c48..c12d7889fb8 100644 --- a/doc/user/search/advanced_search.md +++ b/doc/user/search/advanced_search.md @@ -5,7 +5,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated type: reference --- -# Advanced search **(PREMIUM)** +# Advanced search **(PREMIUM ALL)** > Moved to GitLab Premium in 13.9. diff --git a/doc/user/search/exact_code_search.md b/doc/user/search/exact_code_search.md index 469d91b5194..8a64dc9e70f 100644 --- a/doc/user/search/exact_code_search.md +++ b/doc/user/search/exact_code_search.md @@ -5,7 +5,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated type: reference --- -# Exact Code Search **(PREMIUM)** +# Exact Code Search **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/105049) in GitLab 15.9 [with a flag](../../administration/feature_flags.md) named `index_code_with_zoekt` for indexing and `search_code_with_zoekt` for searching. Both are disabled by default. diff --git a/doc/user/shortcuts.md b/doc/user/shortcuts.md index 0467108c2ca..d8b4d147d24 100644 --- a/doc/user/shortcuts.md +++ b/doc/user/shortcuts.md @@ -311,7 +311,7 @@ These shortcuts are available when using a [filtered search input](search/index. | <kbd>Command</kbd> | <kbd>Delete</kbd> | Clear entire search filter. | | <kbd>Option</kbd> | <kbd>Control</kbd> + <kbd>Delete</kbd> | Clear one token at a time. | -## Epics **(PREMIUM)** +## Epics **(PREMIUM ALL)** These shortcuts are available when viewing [epics](group/epics/index.md): diff --git a/doc/user/storage_management_automation.md b/doc/user/storage_management_automation.md index 0713daf95cd..210aca4ee35 100644 --- a/doc/user/storage_management_automation.md +++ b/doc/user/storage_management_automation.md @@ -649,7 +649,7 @@ python3 get_all_cicd_config_artifacts_expiry.py The `get_all_cicd_config_artifacts_expiry.py` script is located in the [GitLab API with Python project](https://gitlab.com/gitlab-de/use-cases/gitlab-api/gitlab-api-python/). -Alternatively, you can use [advanced search](search/advanced_search.md) with API requests. The following example uses the [scope: blobs](../api/search.md#scope-blobs-premium-2) to searches for the string `artifacts` in all `*.yml` files: +Alternatively, you can use [advanced search](search/advanced_search.md) with API requests. The following example uses the [scope: blobs](../api/search.md#scope-blobs-premium-all-2) to searches for the string `artifacts` in all `*.yml` files: ```shell # https://gitlab.com/gitlab-de/playground/artifact-gen-group/gen-job-artifacts-expiry-included-jobs diff --git a/doc/user/tasks.md b/doc/user/tasks.md index ee45923b180..c340bb736ef 100644 --- a/doc/user/tasks.md +++ b/doc/user/tasks.md @@ -269,7 +269,7 @@ To add a task to a milestone: If a task already belongs to a milestone, the dropdown list shows the current milestone. 1. From the dropdown list, select the milestone to be associated with the task. -## Set task weight **(PREMIUM)** +## Set task weight **(PREMIUM ALL)** > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/362550) in GitLab 15.3. @@ -287,7 +287,7 @@ To set issue weight of a task: 1. Next to **Weight**, enter a whole, positive number. 1. Select the close icon (**{close}**). -## Add a task to an iteration **(PREMIUM)** +## Add a task to an iteration **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/367456) in GitLab 15.5 [with a flag](../administration/feature_flags.md) named `work_items_mvc_2`. Disabled by default. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/367456) to feature flag named `work_items_mvc` in GitLab 15.7. Disabled by default. diff --git a/doc/user/workspace/configuration.md b/doc/user/workspace/configuration.md index eea31e5c39e..3900c95e41a 100644 --- a/doc/user/workspace/configuration.md +++ b/doc/user/workspace/configuration.md @@ -4,7 +4,7 @@ group: IDE info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Workspace configuration (Beta) **(PREMIUM)** +# Workspace configuration (Beta) **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/112397) in GitLab 15.11 [with a flag](../../administration/feature_flags.md) named `remote_development_feature_flag`. Disabled by default. > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/391543) in GitLab 16.0. diff --git a/doc/user/workspace/create_image.md b/doc/user/workspace/create_image.md index 6ec79a49196..43140a622e0 100644 --- a/doc/user/workspace/create_image.md +++ b/doc/user/workspace/create_image.md @@ -4,7 +4,7 @@ group: IDE info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Tutorial: Create a custom workspace image that supports arbitrary user IDs (Beta) **(PREMIUM)** +# Tutorial: Create a custom workspace image that supports arbitrary user IDs (Beta) **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/112397) in GitLab 15.11 [with a flag](../../administration/feature_flags.md) named `remote_development_feature_flag`. Disabled by default. > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/391543) in GitLab 16.0. diff --git a/doc/user/workspace/index.md b/doc/user/workspace/index.md index a39f36a6a59..51e3e905a92 100644 --- a/doc/user/workspace/index.md +++ b/doc/user/workspace/index.md @@ -4,7 +4,7 @@ group: IDE info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- -# Workspaces (Beta) **(PREMIUM)** +# Workspaces (Beta) **(PREMIUM ALL)** > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/112397) in GitLab 15.11 [with a flag](../../administration/feature_flags.md) named `remote_development_feature_flag`. Disabled by default. > - [Enabled on GitLab.com and self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/391543) in GitLab 16.0. diff --git a/lib/gitlab/rack_attack.rb b/lib/gitlab/rack_attack.rb index 6e8d30aa8d6..829b305d1ee 100644 --- a/lib/gitlab/rack_attack.rb +++ b/lib/gitlab/rack_attack.rb @@ -81,53 +81,6 @@ module Gitlab user_allowlist end - ThrottleDefinition = Struct.new(:options, :request_identifier) - DEFS = { - 'throttle_unauthenticated_web' => ThrottleDefinition.new( - Gitlab::Throttle.unauthenticated_web_options, - ->(req) { req.ip if req.throttle_unauthenticated_web? } - ), - # Product analytics feature is in experimental stage. - # At this point we want to limit amount of events registered - # per application (aid stands for application id). - 'throttle_product_analytics_collector' => ThrottleDefinition.new( - { limit: 100, period: 60 }, - ->(req) { req.params['aid'] if req.product_analytics_collector_request? } - ), - 'throttle_authenticated_web' => ThrottleDefinition.new( - Gitlab::Throttle.authenticated_web_options, - ->(req) { req.throttled_identifer([:api, :rss, :ics]) if req.throttle_authenticated_web? } - ), - 'throttle_unauthenticated_protected_paths' => ThrottleDefinition.new( - Gitlab::Throttle.protected_paths_options, - ->(req) { req.ip if req.throttle_unauthenticated_protected_paths? } - ), - 'throttle_authenticated_protected_paths_api' => ThrottleDefinition.new( - Gitlab::Throttle.protected_paths_options, - ->(req) { req.throttled_identifer([:api]) if req.throttle_authenticated_protected_paths_api? } - ), - 'throttle_authenticated_protected_paths_web' => ThrottleDefinition.new( - Gitlab::Throttle.protected_paths_options, - ->(req) { req.throttled_identifer([:api, :rss, :ics]) if req.throttle_authenticated_protected_paths_web? } - ), - 'throttle_unauthenticated_get_protected_paths' => ThrottleDefinition.new( - Gitlab::Throttle.protected_paths_options, - ->(req) { req.ip if req.throttle_unauthenticated_get_protected_paths? } - ), - 'throttle_authenticated_get_protected_paths_api' => ThrottleDefinition.new( - Gitlab::Throttle.protected_paths_options, - ->(req) { req.throttled_identifer([:api]) if req.throttle_authenticated_get_protected_paths_api? } - ), - 'throttle_authenticated_get_protected_paths_web' => ThrottleDefinition.new( - Gitlab::Throttle.protected_paths_options, - ->(req) { req.throttled_identifer([:api, :rss, :ics]) if req.throttle_authenticated_get_protected_paths_web? } - ), - 'throttle_authenticated_git_lfs' => ThrottleDefinition.new( - Gitlab::Throttle.throttle_authenticated_git_lfs_options, - ->(req) { req.throttled_identifer([:api]) if req.throttle_authenticated_git_lfs? } - ) - }.freeze - def self.configure_throttles(rack_attack) # Each of these settings follows the same pattern of specifying separate # authenticated and unauthenticated rates via settings @@ -147,8 +100,49 @@ module Gitlab end end - DEFS.each do |name, definition| - throttle_or_track(rack_attack, name, definition.options, &definition.request_identifier) + throttle_or_track(rack_attack, 'throttle_unauthenticated_web', Gitlab::Throttle.unauthenticated_web_options) do |req| + if req.throttle_unauthenticated_web? + req.ip + end + end + + # Product analytics feature is in experimental stage. + # At this point we want to limit amount of events registered + # per application (aid stands for application id). + throttle_or_track(rack_attack, 'throttle_product_analytics_collector', limit: 100, period: 60) do |req| + if req.product_analytics_collector_request? + req.params['aid'] + end + end + + throttle_or_track(rack_attack, 'throttle_authenticated_web', Gitlab::Throttle.authenticated_web_options) do |req| + if req.throttle_authenticated_web? + req.throttled_identifer([:api, :rss, :ics]) + end + end + + throttle_or_track(rack_attack, 'throttle_unauthenticated_protected_paths', Gitlab::Throttle.protected_paths_options) do |req| + if req.throttle_unauthenticated_protected_paths? + req.ip + end + end + + throttle_or_track(rack_attack, 'throttle_authenticated_protected_paths_api', Gitlab::Throttle.protected_paths_options) do |req| + if req.throttle_authenticated_protected_paths_api? + req.throttled_identifer([:api]) + end + end + + throttle_or_track(rack_attack, 'throttle_authenticated_protected_paths_web', Gitlab::Throttle.protected_paths_options) do |req| + if req.throttle_authenticated_protected_paths_web? + req.throttled_identifer([:api, :rss, :ics]) + end + end + + throttle_or_track(rack_attack, 'throttle_authenticated_git_lfs', Gitlab::Throttle.throttle_authenticated_git_lfs_options) do |req| + if req.throttle_authenticated_git_lfs? + req.throttled_identifer([:api]) + end end rack_attack.safelist('throttle_bypass_header') do |req| diff --git a/lib/gitlab/rack_attack/request.rb b/lib/gitlab/rack_attack/request.rb index a03116f5bb2..d7abacb5b67 100644 --- a/lib/gitlab/rack_attack/request.rb +++ b/lib/gitlab/rack_attack/request.rb @@ -71,10 +71,6 @@ module Gitlab matches?(protected_paths_regex) end - def get_request_protected_path? - matches?(protected_paths_for_get_request_regex) - end - def throttle?(throttle, authenticated:) fragment = Gitlab::Throttle.throttle_fragment!(throttle, authenticated: authenticated) @@ -137,28 +133,6 @@ module Gitlab Gitlab::Throttle.protected_paths_enabled? end - def throttle_unauthenticated_get_protected_paths? - get? && - !should_be_skipped? && - get_request_protected_path? && - Gitlab::Throttle.protected_paths_enabled? && - unauthenticated? - end - - def throttle_authenticated_get_protected_paths_api? - get? && - api_request? && - get_request_protected_path? && - Gitlab::Throttle.protected_paths_enabled? - end - - def throttle_authenticated_get_protected_paths_web? - get? && - web_request? && - get_request_protected_path? && - Gitlab::Throttle.protected_paths_enabled? - end - def throttle_unauthenticated_packages_api? packages_api_path? && Gitlab::Throttle.settings.throttle_unauthenticated_packages_api_enabled && @@ -225,14 +199,6 @@ module Gitlab Regexp.union(protected_paths.map { |path| /\A#{Regexp.escape(path)}/ }) end - def protected_paths_for_get_request - Gitlab::CurrentSettings.current_application_settings.protected_paths_for_get_request - end - - def protected_paths_for_get_request_regex - Regexp.union(protected_paths_for_get_request.map { |path| /\A#{Regexp.escape(path)}/ }) - end - def packages_api_path? matches?(::Gitlab::Regex::Packages::API_PATH_REGEX) end diff --git a/locale/gitlab.pot b/locale/gitlab.pot index cf5c43ad559..ad2f9c72fd1 100644 --- a/locale/gitlab.pot +++ b/locale/gitlab.pot @@ -17874,7 +17874,7 @@ msgstr "" msgid "Enable or disable version check and Service Ping." msgstr "" -msgid "Enable rate limiting for requests to the specified paths" +msgid "Enable rate limiting for POST requests to the specified paths" msgstr "" msgid "Enable reCAPTCHA" @@ -33799,10 +33799,7 @@ msgstr "" msgid "Path:" msgstr "" -msgid "Paths with rate limiting for GET requests" -msgstr "" - -msgid "Paths with rate limiting for POST requests" +msgid "Paths to protect with rate limiting" msgstr "" msgid "Pause" diff --git a/spec/lib/gitlab/rack_attack/request_spec.rb b/spec/lib/gitlab/rack_attack/request_spec.rb index 9d2144f75db..e8433d99d15 100644 --- a/spec/lib/gitlab/rack_attack/request_spec.rb +++ b/spec/lib/gitlab/rack_attack/request_spec.rb @@ -249,39 +249,6 @@ RSpec.describe Gitlab::RackAttack::Request do end end - describe '#get_request_protected_path?' do - subject { request.get_request_protected_path? } - - before do - stub_application_setting( - protected_paths_for_get_request: %w[/protected /secure]) - end - - where(:path, :expected) do - '/' | false - '/groups' | false - '/foo/protected' | false - '/foo/secure' | false - - '/protected' | true - '/secure' | true - '/secure/' | true - '/secure/foo' | true - end - - with_them do - it { is_expected.to eq(expected) } - - context 'when the application is mounted at a relative URL' do - before do - stub_config_setting(relative_url_root: '/gitlab/root') - end - - it { is_expected.to eq(expected) } - end - end - end - describe '#frontend_request?', :allow_forgery_protection do subject { request.send(:frontend_request?) } diff --git a/spec/requests/rack_attack_global_spec.rb b/spec/requests/rack_attack_global_spec.rb index 3f5cd24f3dd..0dd8a15c3a4 100644 --- a/spec/requests/rack_attack_global_spec.rb +++ b/spec/requests/rack_attack_global_spec.rb @@ -320,120 +320,6 @@ feature_category: :system_access do end end - describe 'protected paths for get' do - let(:request_method) { 'GET' } - - context 'unauthenticated requests' do - let(:protected_path_for_get_request_that_does_not_require_authentication) do - '/users/sign_in' - end - - def do_request - get protected_path_for_get_request_that_does_not_require_authentication - end - - before do - settings_to_set[:throttle_protected_paths_requests_per_period] = requests_per_period # 1 - settings_to_set[:throttle_protected_paths_period_in_seconds] = period_in_seconds # 10_000 - settings_to_set[:protected_paths_for_get_request] = %w[/users/sign_in] - end - - context 'when protected paths throttle is disabled' do - before do - settings_to_set[:throttle_protected_paths_enabled] = false - stub_application_setting(settings_to_set) - end - - it 'allows requests over the rate limit' do - (1 + requests_per_period).times do - do_request - expect(response).to have_gitlab_http_status(:ok) - end - end - end - - context 'when protected paths throttle is enabled' do - before do - settings_to_set[:throttle_protected_paths_enabled] = true - stub_application_setting(settings_to_set) - end - - it 'rejects requests over the rate limit' do - requests_per_period.times do - do_request - expect(response).to have_gitlab_http_status(:ok) - end - - expect_rejection { get protected_path_for_get_request_that_does_not_require_authentication } - end - - it 'allows GET requests to unprotected paths over the rate limit' do - (1 + requests_per_period).times do - get '/api/graphql' - expect(response).to have_gitlab_http_status(:ok) - end - end - - it_behaves_like 'tracking when dry-run mode is set' do - let(:throttle_name) { 'throttle_unauthenticated_get_protected_paths' } - end - end - end - - context 'API requests authenticated with personal access token', :api do - let(:user) { create(:user) } - let(:token) { create(:personal_access_token, user: user) } - let(:other_user) { create(:user) } - let(:other_user_token) { create(:personal_access_token, user: other_user) } - let(:throttle_setting_prefix) { 'throttle_protected_paths' } - let(:api_partial_url) { '/user/emails' } - - let(:protected_paths_for_get_request) do - [ - '/api/v4/user/emails' - ] - end - - before do - settings_to_set[:protected_paths_for_get_request] = protected_paths_for_get_request - stub_application_setting(settings_to_set) - end - - context 'with the token in the query string' do - let(:request_args) { [api(api_partial_url, personal_access_token: token), {}] } - let(:other_user_request_args) { [api(api_partial_url, personal_access_token: other_user_token), {}] } - - it_behaves_like 'rate-limited user based token-authenticated requests' - end - - context 'with the token in the headers' do - let(:request_args) { api_get_args_with_token_headers(api_partial_url, personal_access_token_headers(token)) } - let(:other_user_request_args) { api_get_args_with_token_headers(api_partial_url, personal_access_token_headers(other_user_token)) } - - it_behaves_like 'rate-limited user based token-authenticated requests' - end - end - - describe 'web requests authenticated with regular login' do - let(:throttle_setting_prefix) { 'throttle_protected_paths' } - let(:user) { create(:user) } - let(:url_that_requires_authentication) { '/users/confirmation' } - - let(:protected_paths_for_get_request) do - [ - url_that_requires_authentication - ] - end - - before do - settings_to_set[:protected_paths_for_get_request] = protected_paths_for_get_request - stub_application_setting(settings_to_set) - end - - it_behaves_like 'rate-limited web authenticated requests' - end - end - describe 'Packages API' do let(:request_method) { 'GET' } diff --git a/spec/services/application_settings/update_service_spec.rb b/spec/services/application_settings/update_service_spec.rb index 62bb42740c2..9d73a4a6cee 100644 --- a/spec/services/application_settings/update_service_spec.rb +++ b/spec/services/application_settings/update_service_spec.rb @@ -331,8 +331,7 @@ RSpec.describe ApplicationSettings::UpdateService do throttle_protected_paths_enabled: 1, throttle_protected_paths_period_in_seconds: 600, throttle_protected_paths_requests_per_period: 100, - protected_paths_raw: "/users/password\r\n/users/sign_in\r\n", - protected_paths_for_get_request_raw: "/users/password\r\n/users/sign_up\r\n" + protected_paths_raw: "/users/password\r\n/users/sign_in\r\n" } end @@ -345,7 +344,6 @@ RSpec.describe ApplicationSettings::UpdateService do expect(application_settings.throttle_protected_paths_period_in_seconds).to eq(600) expect(application_settings.throttle_protected_paths_requests_per_period).to eq(100) expect(application_settings.protected_paths).to eq(['/users/password', '/users/sign_in']) - expect(application_settings.protected_paths_for_get_request).to match_array(['/users/password', '/users/sign_up']) end end diff --git a/spec/support/shared_examples/requests/rack_attack_shared_examples.rb b/spec/support/shared_examples/requests/rack_attack_shared_examples.rb index 48d3e438322..dafa324b3c6 100644 --- a/spec/support/shared_examples/requests/rack_attack_shared_examples.rb +++ b/spec/support/shared_examples/requests/rack_attack_shared_examples.rb @@ -148,12 +148,6 @@ RSpec.shared_examples 'rate-limited token requests' do expect(response).not_to have_gitlab_http_status(:too_many_requests) end - matched = throttle_types[throttle_setting_prefix] - - if request_method == 'GET' && throttle_setting_prefix == 'throttle_protected_paths' - matched = 'throttle_authenticated_get_protected_paths_api' - end - arguments = a_hash_including({ message: 'Rack_Attack', status: 429, @@ -161,7 +155,7 @@ RSpec.shared_examples 'rate-limited token requests' do remote_ip: '127.0.0.1', request_method: request_method, path: request_args.first, - matched: matched + matched: throttle_types[throttle_setting_prefix] }.merge(log_data)) expect(Gitlab::AuthLogger).to receive(:error).with(arguments).once @@ -172,14 +166,7 @@ RSpec.shared_examples 'rate-limited token requests' do end it_behaves_like 'tracking when dry-run mode is set' do - let(:throttle_name) do - name = throttle_types[throttle_setting_prefix] - if request_method == 'GET' && throttle_setting_prefix == 'throttle_protected_paths' - name = 'throttle_authenticated_get_protected_paths_api' - end - - name - end + let(:throttle_name) { throttle_types[throttle_setting_prefix] } def do_request make_request(request_args) @@ -328,13 +315,7 @@ RSpec.shared_examples 'rate-limited web authenticated requests' do expect(response).not_to have_gitlab_http_status(:too_many_requests) end - matched = throttle_types[throttle_setting_prefix] - - if request_method == 'GET' && throttle_setting_prefix == 'throttle_protected_paths' - matched = 'throttle_authenticated_get_protected_paths_web' - end - - arguments = a_hash_including( + arguments = a_hash_including({ message: 'Rack_Attack', status: 429, env: :throttle, @@ -343,22 +324,15 @@ RSpec.shared_examples 'rate-limited web authenticated requests' do path: url_that_requires_authentication, user_id: user.id, 'meta.user' => user.username, - matched: matched - ) + matched: throttle_types[throttle_setting_prefix] + }) expect(Gitlab::AuthLogger).to receive(:error).with(arguments).once expect { request_authenticated_web_url }.not_to exceed_query_limit(control_count) end it_behaves_like 'tracking when dry-run mode is set' do - let(:throttle_name) do - name = throttle_types[throttle_setting_prefix] - if request_method == 'GET' && throttle_setting_prefix == 'throttle_protected_paths' - name = 'throttle_authenticated_get_protected_paths_web' - end - - name - end + let(:throttle_name) { throttle_types[throttle_setting_prefix] } def do_request request_authenticated_web_url |