diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-18 06:08:39 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-18 06:08:39 +0300 |
| commit | 1a683ed158e0d1b37b35cc24e219e57a1719642b (patch) | |
| tree | 6c46f5e5542ef3bd3c3736b5fb63e2e4209958e1 /doc/user/packages | |
| parent | ccceee21749ddf0dc974337aeb4aba2bf2bbb00b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/packages')
| -rw-r--r-- | doc/user/packages/container_registry/troubleshoot_container_registry.md | 2 | ||||
| -rw-r--r-- | doc/user/packages/maven_repository/index.md | 2 | ||||
| -rw-r--r-- | doc/user/packages/package_registry/index.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/user/packages/container_registry/troubleshoot_container_registry.md b/doc/user/packages/container_registry/troubleshoot_container_registry.md index 729f4919188..34c86a90d49 100644 --- a/doc/user/packages/container_registry/troubleshoot_container_registry.md +++ b/doc/user/packages/container_registry/troubleshoot_container_registry.md @@ -125,5 +125,5 @@ This error happens when your authentication token expires before the image push the Container Registry on self-managed GitLab instances expire every five minutes. On GitLab.com, the token expiration time is set to 15 minutes. -If you are using self-managed GitLab, you can ask an administrator to +If you are using self-managed GitLab, an administrator can [increase the token duration](../../../administration/packages/container_registry.md#increase-token-duration). diff --git a/doc/user/packages/maven_repository/index.md b/doc/user/packages/maven_repository/index.md index bcc55af65bc..f06db7ef1ac 100644 --- a/doc/user/packages/maven_repository/index.md +++ b/doc/user/packages/maven_repository/index.md @@ -490,7 +490,7 @@ Your changes are automatically saved. ### Request forwarding to Maven Central FLAG: -By default this feature is not available for self-managed. To make it available, ask an administrator to [enable the feature flag](../../../administration/feature_flags.md) named `maven_central_request_forwarding`. +By default this feature is not available for self-managed. To make it available, an administrator can [enable the feature flag](../../../administration/feature_flags.md) named `maven_central_request_forwarding`. This feature is not available for SaaS users. When a Maven package is not found in the Package Registry, the request is forwarded diff --git a/doc/user/packages/package_registry/index.md b/doc/user/packages/package_registry/index.md index ce300e26f8c..d06b1ababb8 100644 --- a/doc/user/packages/package_registry/index.md +++ b/doc/user/packages/package_registry/index.md @@ -161,7 +161,7 @@ Registry disables all Package Registry operations. FLAG: On self-managed GitLab, by default this feature is available. To disable it, -ask an administrator to [disable the feature flag](../../../administration/feature_flags.md) named `package_registry_access_level`. +an administrator can [disable the feature flag](../../../administration/feature_flags.md) named `package_registry_access_level`. If you want to allow anyone (everyone on the internet) to pull from the Package Registry, no matter what the project visibility is, you can use the additional toggle `Allow anyone to pull from Package Registry` that appears when the project visibility is Private or Internal. |