diff options
| author | Zeger-Jan van de Weg <git@zjvandeweg.nl> | 2018-04-12 09:12:21 +0200 |
|---|---|---|
| committer | Zeger-Jan van de Weg <git@zjvandeweg.nl> | 2018-04-12 15:23:36 +0200 |
| commit | a752c56ca82d6f0fdee340f5d494347a4aa90072 (patch) | |
| tree | 721698bb52f983d58031cd510732546a323d4e71 /config | |
| parent | b2f57a561f0540f8e33c2d580252e6f95e9cf182 (diff) | |
| download | gitlab-ce-a752c56ca82d6f0fdee340f5d494347a4aa90072.tar.gz | |
Deprecate legacy disk paths
Direct disk access is impossible on environments where components run in
their own container. There for constructing the path should not be done
except for exceptional cases.
One of the considerations, instead of logging, was to use Sentry. For
now I've chosen not to use this as the impact of this change is hard to
determine. Getting this in now will allow us to checkout the impact on
dev.gitlab.org and staging.
Diffstat (limited to 'config')
| -rw-r--r-- | config/initializers/deprecations.rb | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/config/initializers/deprecations.rb b/config/initializers/deprecations.rb new file mode 100644 index 00000000000..add744accee --- /dev/null +++ b/config/initializers/deprecations.rb @@ -0,0 +1,5 @@ +deprecator = ActiveSupport::Deprecation.new('11.0', 'GitLab') + +if Gitlab.inc_controlled? || Rails.env.development? + ActiveSupport::Deprecation.deprecate_methods(Gitlab::GitalyClient::StorageSettings, :legacy_disk_path, deprecator: deprecator) +end |