gitlab-org--gitlab-foss/config/initializers/deprecations.rb

# frozen_string_literal: true

if Rails.env.development? || ENV['GITLAB_LEGACY_PATH_LOG_MESSAGE']
  deprecator = ActiveSupport::Deprecation.new('11.0', 'GitLab')

  deprecator.behavior = -> (message, callstack) {
    Gitlab::AppLogger.warn("#{message}: #{callstack[1..20].join}")
  }

  ActiveSupport::Deprecation.deprecate_methods(Gitlab::GitalyClient::StorageSettings, :legacy_disk_path, deprecator: deprecator)
end
Add latest changes from gitlab-org/gitlab@master 2021-02-03 16:09:17 -05:00			`# frozen_string_literal: true`

Conditionally add Gitaly deprecation warnings based on ENV variable 2018-05-17 13:12:48 -04:00			`if Rails.env.development? \|\| ENV['GITLAB_LEGACY_PATH_LOG_MESSAGE']`
More verbose logging for deprecated path access Current logging tells us we've isolated the calls to about 5 call sites, now we'd like to know what is calling these methods. 2018-05-14 09:08:51 -04:00			`deprecator = ActiveSupport::Deprecation.new('11.0', 'GitLab')`

			`deprecator.behavior = -> (message, callstack) {`
Add latest changes from gitlab-org/gitlab@master 2020-09-09 08:08:22 -04:00			`Gitlab::AppLogger.warn("#{message}: #{callstack[1..20].join}")`
More verbose logging for deprecated path access Current logging tells us we've isolated the calls to about 5 call sites, now we'd like to know what is calling these methods. 2018-05-14 09:08:51 -04:00			`}`

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. 2018-04-12 03:12:21 -04:00			`ActiveSupport::Deprecation.deprecate_methods(Gitlab::GitalyClient::StorageSettings, :legacy_disk_path, deprecator: deprecator)`
			`end`