From 84d1bd786125c1c14a3ba5f63e38a4cc736a9027 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 16 Jan 2024 10:42:19 +0000 Subject: Add latest changes from gitlab-org/gitlab@16-8-stable-ee --- .../16-8-deprecate-pg_schema-backup-setting.yml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml (limited to 'data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml') diff --git a/data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml b/data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml new file mode 100644 index 00000000000..4edb2c8fde2 --- /dev/null +++ b/data/deprecations/16-8-deprecate-pg_schema-backup-setting.yml @@ -0,0 +1,14 @@ +- title: "Support for setting custom schema for backup is deprecated" + announcement_milestone: "16.8" + removal_milestone: "17.0" + breaking_change: true + reporter: sranasinghe + stage: core platform + issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/435210 + body: | + You could configure GitLab to use a custom schema for backup, by setting + `gitlab_rails['backup_pg_schema'] = ''` in `/etc/gitlab/gitlab.rb` for Linux package installations, + or by editing `config/gitlab.yml` for self-compiled installations. + + While the configuration setting was available, it had no effect and did not serve the purpose it was intended. + This configuration setting will be removed in GitLab 17.0. -- cgit v1.2.3