diff --git a/doc/administration/geo/replication/datatypes.md b/doc/administration/geo/replication/datatypes.md index 5636ff79189400de12778d693125bbeca0282c2b..8fb62580bbe4cc490955679bd9f3cd90214756a6 100644 --- a/doc/administration/geo/replication/datatypes.md +++ b/doc/administration/geo/replication/datatypes.md @@ -169,3 +169,21 @@ successfully, you must replicate their data using some other means. LFS objects from replicating](https://gitlab.com/gitlab-org/gitlab/-/issues/32696). - (*3*): If you are using Object Storage, the replication can be performed by the Object Storage provider if supported. Please see [Geo with Object Storage](object_storage.md) + +### Package file replication behind a feature flag + +Package file replication is behind a feature flag - `geo_self_service_framework_replication`, which is enabled by default. + +For GitLab self-managed instances, GitLab administrators can opt to disable them. + +To disable: + +```ruby +Feature.disable(:geo_self_service_framework_replication) +``` + +To enable: + +```ruby +Feature.enable(:geo_self_service_framework_replication) +``` diff --git a/doc/api/protected_branches.md b/doc/api/protected_branches.md index 4206fe6a565939962ed6430a97604c43b957b326..a1f42958c368c1b6c6a90578c8f12322efec5e34 100644 --- a/doc/api/protected_branches.md +++ b/doc/api/protected_branches.md @@ -248,7 +248,7 @@ Example response: ### Example with user / group level access **(STARTER)** 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#restricting-push-and-merge-access-to-certain-users-starter) and were [added to the API in](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/3516) in GitLab 10.3 EE. +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#restricting-push-and-merge-access-to-certain-users-starter) and were [added to the API in](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/3516) GitLab 10.3 EE. ```shell curl --request POST --header "PRIVATE-TOKEN: " "https://gitlab.example.com/api/v4/projects/5/protected_branches?name=*-stable&allowed_to_push%5B%5D%5Buser_id%5D=1" diff --git a/doc/api/scim.md b/doc/api/scim.md index 7c8da37a949e3586965ee7264f68643c14e30ed4..bd86408ee63d354c80d3d805d205bb1d82d20c6c 100644 --- a/doc/api/scim.md +++ b/doc/api/scim.md @@ -2,7 +2,7 @@ > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/9388) in [GitLab Silver](https://about.gitlab.com/pricing/) 11.10. -The SCIM API implements the [the RFC7644 protocol](https://tools.ietf.org/html/rfc7644). +The SCIM API implements [the RFC7644 protocol](https://tools.ietf.org/html/rfc7644). CAUTION: **Caution:** This API is for internal system use for connecting with a SCIM provider. While it can be used directly, it is subject to change without notice. diff --git a/doc/ci/environments/deployment_safety.md b/doc/ci/environments/deployment_safety.md index a4ff164a5ba40939bffb5a7f0d627a196a57f84d..c993fd5f5d4528a3b13dea7ea2b317f9fec2af5f 100644 --- a/doc/ci/environments/deployment_safety.md +++ b/doc/ci/environments/deployment_safety.md @@ -26,7 +26,7 @@ Pipeline jobs in GitLab CI/CD run in parallel, so it's possible that two deploym jobs in two different pipelines attempt to deploy to the same environment at the same time. This is not desired behavior as deployments should happen sequentially. -You can ensure only one deployment job runs at a time with the [`resource_group` keyword](../yaml/README.md#resource_group) keyword in your `.gitlab-ci.yml`. +You can ensure only one deployment job runs at a time with the [`resource_group` keyword](../yaml/README.md#resource_group) in your `.gitlab-ci.yml`. For example: diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md index afd676cf897fc75c7b9bd7150b8ce22acf367714..756eb66fd299d188873b4131d7707c18c0e1c81f 100644 --- a/doc/user/group/saml_sso/index.md +++ b/doc/user/group/saml_sso/index.md @@ -259,7 +259,7 @@ Group SAML SSO helps if you need to allow access via multiple SAML identity prov To proceed with configuring Group SAML SSO instead, you'll need to enable the `group_saml` OmniAuth provider. This can be done from: -- `gitlab.rb` for GitLab [Omnibus installations](#omnibus-installations). +- `gitlab.rb` for [Omnibus GitLab installations](#omnibus-installations). - `gitlab/config/gitlab.yml` for [source installations](#source-installations). ### Limitations diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md index 0425ca56285453134a8dc4cc31923bea3377b79c..1c28ff14ad77cfae76bdd0f033b48a31ffda9ca0 100644 --- a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md +++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md @@ -100,7 +100,7 @@ as it most likely won't work if you set an [`MX` record](dns_concepts.md#mx-reco Subdomains (`subdomain.example.com`) require: -- A DNS [CNAME record](dns_concepts.md#cname-record) record pointing your subdomain to the Pages server. +- A DNS [CNAME record](dns_concepts.md#cname-record) pointing your subdomain to the Pages server. - A DNS [TXT record](dns_concepts.md#txt-record) to verify your domain's ownership. | From | DNS Record | To |