diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-05 09:19:15 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-04-05 09:19:15 +0000 |
| commit | 508f0c4ee719abb1294684eea4a63aa44cd23597 (patch) | |
| tree | 1af8199669fe0e9086bc57ba91510e80da093ffa /doc/update/removals.md | |
| parent | 9a0dd27b634dde1f947beafcf822efef1cd2dcfc (diff) | |
| download | gitlab-ce-508f0c4ee719abb1294684eea4a63aa44cd23597.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/update/removals.md')
| -rw-r--r-- | doc/update/removals.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/update/removals.md b/doc/update/removals.md index 6874ab9fe2e..843604b8a18 100644 --- a/doc/update/removals.md +++ b/doc/update/removals.md @@ -247,7 +247,7 @@ If your object storage provider does not support `background_upload`, please [mi #### Encrypted S3 buckets -Additionally, this also breaks the use of [encrypted S3 buckets](https://docs.gitlab.com/ee/administration/object_storage.html#encrypted-s3-buckets) with [storage-specific configuration form](https://docs.gitlab.com/ee/administration/object_storage.html#storage-specific-configuration). +Additionally, this also breaks the use of [encrypted S3 buckets](https://docs.gitlab.com/ee/administration/object_storage.html#encrypted-s3-buckets) with [storage-specific configuration form](https://docs.gitlab.com/ee/administration/object_storage.html#configure-each-object-type-to-define-its-own-storage-connection-storage-specific-form). If your S3 buckets have [SSE-S3 or SSE-KMS encryption enabled](https://docs.aws.amazon.com/kms/latest/developerguide/services-s3.html), please [migrate your configuration to use consolidated object storage form](https://docs.gitlab.com/ee/administration/object_storage.html#transition-to-consolidated-form) before upgrading to GitLab 15.0. Otherwise, you may start getting `ETag mismatch` errors during objects upload. @@ -265,7 +265,7 @@ Some users found that they could specify a path prefix to the bucket. In direct If you have set a prefix, you can use a workaround to revert to background uploads: -1. Continue to use [storage-specific configuration](https://docs.gitlab.com/ee/administration/object_storage.html#storage-specific-configuration). +1. Continue to use [storage-specific configuration](https://docs.gitlab.com/ee/administration/object_storage.html#configure-each-object-type-to-define-its-own-storage-connection-storage-specific-form). 1. In Omnibus GitLab, set the `GITLAB_LEGACY_BACKGROUND_UPLOADS` to re-enable background uploads: ```ruby |